Self-host Termix with Levelrail
A web-based SSH, RDP, and VNC terminal manager for organizing and connecting to every server from one dashboard.
- AuthorTermix-SSH
- LicenceApache-2.0
- Memory256 MiB
- Archarm64
- Services2
How to self-host Termix
-
Pull the images
2 images are pulled on your server.
Show images
guacamole/guacd:1.6.0ghcr.io/lukegus/termix:2.6.1
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
3 settings are 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.
Termix requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Termix. 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 Termix docs page.
Deploy Termix your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Termix from the CLI
levelrail-cli templates deploy termix --name my-termix Deploy Termix with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/termix/deploy Termix configuration
Termix services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| guacd | guacamole/guacd:1.6.0 | none | none |
| termix | ghcr.io/lukegus/termix:2.6.1 | 8080 | termix_data -> /app/data |
Termix environment variables
| Variable | Service | Value |
|---|---|---|
| GUACD_HOST | termix | Preset by the template |
| GUACD_RECORDING_PATH | termix | Preset by the template |
| PORT | termix | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: termix_data -> /app/data
Termix FAQ
How much memory does Termix need?
The catalog lists about 256 MiB of memory for Termix across its 2 services.
Does Termix run on arm64?
For Termix, an arm64 image is published; amd64 is image published.
What licence is Termix under?
Termix is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Termix need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Termix use?
Termix listens on port 8080 inside the stack.
Where does Termix keep its data?
In a named volume: termix_data mounted at /app/data.
Can I deploy Termix 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 Termix, 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 guacamole/guacd:1.6.0, ghcr.io/lukegus/termix:2.6.1 is what you deploy there.