Erugo on Ubuntu 24.04 LTS

Why the cloudimg image

Erugo normally creates its first administrator through a setup wizard that anyone can complete simply by being the first to open the site, so cloudimg closes that door before the image ever ships. The single administrator account is created during the build, the wizard is permanently sealed, and the password is replaced with a unique random one on the first boot of every instance, written to a root only file. There is no default login and no two instances share a credential. The application encryption key, the API token signing secret and the TLS certificate are all regenerated per instance too, so nothing cryptographic is shared between customers.

The image is a complete working platform rather than a bare install: the web frontend is compiled at build time and verified to be present and correct, the resumable upload service and the background worker that packages shares are both running as managed services, and scheduled expiry and cleanup jobs are wired up. The web interface is served over HTTPS by default with a per instance certificate. Uploaded files, the database and the application itself sit on a dedicated data disk that is separate from the operating system disk and can be resized independently.

Every build is proven by a real end to end transfer, uploading a file, creating a share, downloading it through the public link and comparing it byte for byte, so the product is known to work and not merely known to respond. The base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide and backed by 24/7 cloudimg support.