Self-host Ampache with Levelrail
A web based audio and video streaming server with a library, playlists, users and a Subsonic compatible API, backed by MariaDB. Finish the install from the first page with the database details shown in the notes.
- Authorampache
- LicenceAGPL-3.0-or-later
- Memory512 MiB
- Services2
How to self-host Ampache
-
Pull the images
2 images are pulled on your server.
Show images
ampache/ampache:8.4.0mariadb:11.8.9
-
Create the app
2 services start in a single Compose app, with 3 named volume mounts for your data, on port 80.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the page and run the installer with database host db, database ampache, user root and the generated root password, then create the admin.
Ampache requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Ampache. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Ampache docs page.
Deploy Ampache your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Ampache from the CLI
levelrail-cli templates install ampache --name my-ampache Deploy Ampache with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/ampache/install \
-d '{
"name": "my-ampache"
}' Ampache configuration
Ampache services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| ampache | ampache/ampache:8.4.0 | 80 | config -> /var/www/html/configmedia -> /media |
| db | mariadb:11.8.9 | none | mariadb_data -> /var/lib/mysql |
Ampache environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_DATABASE | db | Preset by the template |
| MYSQL_ROOT_PASSWORD | db | Generated at deploy |
Ports and volumes
- Ports
- 80
- Volumes
- 3 named mounts: config -> /var/www/html/config, media -> /media, mariadb_data -> /var/lib/mysql
Ampache FAQ
How much memory does Ampache need?
The catalog lists about 512 MiB of memory for Ampache across its 2 services.
Does Ampache run on arm64?
For Ampache, arm64 support is not confirmed; amd64 is unknown.
What licence is Ampache under?
Ampache is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Ampache need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Ampache bundle?
The template includes MySQL, running as its own service.
Which ports does Ampache use?
Ampache listens on port 80 inside the stack.
Where does Ampache keep its data?
In named volumes: config mounted at /var/www/html/config, media mounted at /media and mariadb_data mounted at /var/lib/mysql.
Can I deploy Ampache on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id ampache for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ampache/ampache:8.4.0, mariadb:11.8.9 is what you deploy there.