Skip to content
LLicentivo
Open console

Software store HTTPS deployment, backup and recovery

In production, use a dedicated low-privilege system account to run launch serve, fixing the working directory and configuration path in the service manager. Use systemd for Linux startup and Restart=on-failure to restart after abnormal exits. On Windows, a trusted service manager can run the same launch.exe serve command.

Linux systemd example
/etc/systemd/system/licentivo-launch.service
[Unit]
Description=Licentivo Launch
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=launch
Group=launch
WorkingDirectory=/opt/licentivo-launch
ExecStart=/opt/licentivo-launch/launch serve --config /etc/licentivo-launch/config.yaml
Restart=on-failure
RestartSec=5
UMask=0077
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Create the launch system user with read access to configuration and write access to uploads, then run sudo systemctl daemon-reload and sudo systemctl enable --now licentivo-launch. A deliberate service stop does not trigger failure recovery.

When a reverse proxy provides public HTTPS, bind http_addr to an internal address and set public_url to the HTTPS domain customers actually visit. Confirm that /healthz and /readyz both return 200 before launch.

Check and backup
./launch check --config /etc/licentivo-launch/config.yaml
./launch backup --config /etc/licentivo-launch/config.yaml /secure/backup/launch.launchbackup

Set a separate LAUNCH_BACKUP_PASSPHRASE. The database backup does not include uploaded files; save the upload directory separately. Restore only to an empty database. The command writes a protected PATH.secrets.yaml. After restoring, reconcile payments, refunds, and license changes made after the backup time.