Deploy Funkwhale
Federated music and podcast server: stream, share and follow libraries
Redis
Just deployed
/data
Funkwhale
Just deployed
/srv/funkwhale/data
Just deployed
/var/lib/postgresql/data
Deploy and Host Funkwhale on Railway
Funkwhale is a free, open-source and self-hosted music and podcast server. You upload your music or import it in place, organise it into libraries, playlists and radios, and listen in the browser or in Subsonic-compatible apps. Pods federate over ActivityPub, so people can follow libraries and channels across servers.
About Hosting Funkwhale
A Funkwhale pod has several parts: a Django API served by gunicorn, Celery workers that import uploads and handle federation, Celery beat for scheduled jobs, nginx serving the web app and protected media, plus Postgres and Redis. The API, workers and nginx all need the same media folder. This template runs those four processes in one service with one persistent volume, next to Railway Postgres and Redis. On every start it applies database migrations, creates the first admin once from the template's variables, and keeps public sign-ups closed. Audio files stay on the volume and survive redeploys. Plan on about 1 GB of RAM.
Common Use Cases
- Stream your own music collection from anywhere, in the browser or in Subsonic apps such as DSub, Ultrasonic or Substreamer
- Publish podcasts or audio channels that people can follow from Funkwhale, Mastodon and other fediverse apps
- Share a music library with family, friends or a small community on your own server
Dependencies for Funkwhale Hosting
- Postgres (Railway Postgres) for the database
- Redis (Railway Redis) for the cache and the Celery task queue
Deployment Dependencies
- Funkwhale 2.0.14 official images
funkwhale/apiandfunkwhale/front: https://hub.docker.com/r/funkwhale/api - Funkwhale source and changelog: https://dev.funkwhale.audio/funkwhale/funkwhale
- Funkwhale administrator documentation: https://docs.funkwhale.audio/administrator/
- Template source (Dockerfile and start script): https://github.com/aalfath/funkwhale-railway-template
Implementation Details
After the deploy finishes, open the public URL and log in with the username podadmin (or the one you chose) and the password in the Funkwhale service's FUNKWHALE_ADMIN_PASSWORD variable. Change the password in the web app afterwards: the variable is only used when the admin is first created.
FUNKWHALE_HOSTNAMEdefaults to the Railway domain. If you want a custom domain, add it and setFUNKWHALE_HOSTNAMEto it before you upload music or follow anyone, because federation IDs contain the hostname and can't change later.- Sign-ups are closed. Open them under Administration, Settings, Users if you want other people to register.
- Optional: e-mail (
EMAIL_CONFIG,DEFAULT_FROM_EMAIL), S3 media storage (AWS_*), more workers (CELERYD_CONCURRENCY,FUNKWHALE_WEB_WORKERS, default 2 each) and a bigger upload limit (NGINX_MAX_BODY_SIZE, default 512M). See https://docs.funkwhale.audio/administrator/configuration/env-file.html - To import a large collection in place, copy it into
/srv/funkwhale/data/musicon the volume and runfunkwhale-manage import_filesfrom the service shell, as in https://docs.funkwhale.audio/administrator/manage-script/library.html
Why Deploy Funkwhale on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Funkwhale on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Redis
redis:8.2Funkwhale
aalfath/funkwhale-railway-template