Solo Docs
Run an instance

Compose generator

Make a Docker Compose file for Solo with new passwords, your storage paths and an optional Cloudflare Tunnel.

This generator runs only in your browser. It sends nothing to a server and it saves nothing. The page tells your browser to block all network connections from scripts, so your values cannot leave it. Your browser makes the passwords with crypto.getRandomValues.

To check this, open the developer tools of your browser and look at the network activity while you use the form. The values stay only until you close or reload the page.

Settings

Use solo for an image that you built yourself.
The port on the host. Solo listens on 8080 in the container.
From step 1 of Install. For Google, use the full ID that ends in .apps.googleusercontent.com.
You enter this in the setup wizard. Solo disables the setup account when the wizard is complete.
Only the two containers use it. You do not have to keep a copy.

Enter a directory on the host for each type of data. Leave a field empty to keep that data in a Docker volume.

All projects, the audit log and the data of each extension.
Theme packages that you add. The built-in themes are in the image.
Extension packages. Solo writes here when you install an update from Admin settings.

A Cloudflare Tunnel publishes Solo at a public address with no open port on your router. Cloudflare gives the address its TLS certificate.

Your Compose file

The file holds your passwords and your tunnel token. Keep it private. Do not add it to a public repository.

Next steps

  1. Save the file as docker-compose.yml in an empty directory on the host.
  2. If you entered directories for themes or extensions, make them and give them to the user of the container, UID 1654.
  3. Start Solo:

    docker compose up -d
    
  4. Open the address of the instance and complete the setup wizard with the setup user name and password from above.