7c27f01ab8
With our current self-hosting installation process, this is not longer required. It should be the users responsibility to gain access to his server. For Cloudron managed hosting, this does not apply as we always create servers with ssh keys. Also do not tinker with the sshd configs. The user may choose to use access via password. Fixes #104
Installer
This subfolder contains all resources, which persist across a Cloudron update. Only code and assets, which are part of the updater belong here.
Installer is the name which got inherited from times, where this folder contained much more infrastructure components, like a local webserver to facilitate updates.
installer.sh
The main entry point for initial provisioning and also updates (not upgrades).
It is called from:
- cloudron-setup (during initial provisioning, restoring or upgrade)
- cloudron.js in the box code (during an update)
Two arguments need to be supplied in this order:
- The public url to download the box release tarball
--sourcetarballurl - JSON object which contains the user-data
--data
cloudron-system-setup.sh
This is the systemd unit file script hook, which persists Cloudron updates. Mostly it revolves around setting up various parts of the filesystem, like btrfs volumes and swap files