Self-host The Lounge with Levelrail
A modern web IRC client that stays connected for you, so you can read what you missed from any device. Users are created from the command line, and chat history is kept on a volume.
- Authorthelounge
- LicenceMIT
- Memory256 MiB
- Services1
How to self-host The Lounge
-
Pull the images
One image is pulled on your server.
Show images
thelounge/thelounge:4.5.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9000.
-
Fill in the secrets
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
- Create your first user from the container terminal with thelounge add followed by a username, then sign in at the address.
The Lounge requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive 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 The Lounge. 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 The Lounge docs page.
Deploy The Lounge your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy The Lounge from the CLI
levelrail-cli templates deploy thelounge --name my-thelounge Deploy The Lounge with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/thelounge/deploy The Lounge configuration
The Lounge services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| thelounge | thelounge/thelounge:4.5.2 | 9000 | config -> /var/opt/thelounge |
The Lounge environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9000
- Volumes
- 1 named mount: config -> /var/opt/thelounge
The Lounge FAQ
How much memory does The Lounge need?
The catalog lists about 256 MiB of memory for The Lounge.
Does The Lounge run on arm64?
For The Lounge, arm64 support is not confirmed; amd64 is unknown.
What licence is The Lounge under?
The Lounge is licensed under MIT, which is permissive, with few conditions on reuse.
Does The Lounge need configuration before it starts?
No. The template fills in its own defaults.
Which ports does The Lounge use?
The Lounge listens on port 9000 inside the stack.
Where does The Lounge keep its data?
In a named volume: config mounted at /var/opt/thelounge.
Can I deploy The Lounge on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for The Lounge, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image thelounge/thelounge:4.5.2 is what you deploy there.