Technical installation
Requirements
Section titled “Requirements”- A server with Podman or Docker (amd64 or arm64), permanently on
- A reverse proxy with a TLS certificate — the app marks its session cookie as
Secure, so login will not work over plain HTTP - The application image, which I provide after purchase (a
.tarfile)
Starting it
Section titled “Starting it”# 1. Load the image you were givenpodman load -i aledrogi-chat-amd64.tar
# 2. A volume for the database — it survives image updatespodman volume create shop-data
# 3. Start (port bound locally; the outside world goes through the TLS proxy)podman run -d --name aledrogi --restart unless-stopped \ -v shop-data:/data \ --env-file .env \ -p 127.0.0.1:3000:3000 \ localhost/aledrogi-chat:latestThe entire application state is a single SQLite file under /data on the volume.
A backup of that volume is a backup of the whole application.
First login
Section titled “First login”The starting account’s password is generated at first start and printed once to the log:
podman logs aledrogiAt first login the app forces a change. The minimum length is 12 characters.
The order matters on a fresh install
Section titled “The order matters on a fresh install”The licence binds to your Allegro account, so:
- Log in and change the starting password.
- Configuration → Allegro account → Connect and complete the authorisation.
- Configuration → Licence — paste the key you received and click “Activate”.
Updating
Section titled “Updating”podman load -i aledrogi-chat-amd64.tar # new imagepodman stop aledrogi && podman rm aledrogi# run again with the same parameters — the volume staysData survives, because the database lives on the volume rather than in the container.
Test mode
Section titled “Test mode”The app can run on sample data without connecting to Allegro — useful for clicking through the panel before a real account is attached. The mode is set in the configuration provided at deployment.