Debian 13 Web Terminal (Browser Shell)
A Debian 13 shell you open in a browser, served by ttyd behind an nginx password check. Sessions run in tmux so they survive closed tabs, and the home directory is on a persistent volume. git, Python, Node.js and build tools come preinstalled.
What you get
- One Terminal service on debian:13.7 with ttyd 1.7.7 and tmux
- Password protection with a generated password; never served without a login
- Volume at /home for files, dotfiles and shell history
- User debian with sudo
- No database or API keys
Good for
- A Linux shell from a Chromebook, tablet or locked-down laptop
- Running long scripts or builds in tmux and checking back later
- Learning Linux and shell scripting without a local setup
- Testing scripts and packages on Debian 13
Services in this template
- Terminal · from
baranberkay96/debian-terminal-railway
Questions people ask
How do I log in?
Your browser asks for a user name and password. The user is debian and the password is the generated PASSWORD value on the service Variables tab. You land in a tmux session named main.
What survives a redeploy?
Everything under /home/debian, including files, shell history, Python virtualenvs and npm globals. Running processes and apt-installed packages reset, unless you list packages in APT_PACKAGES or in ~/.config/debian-terminal/apt-packages.
Can several people share it?
It is a single-user machine on one volume, so keep one replica. For a team, deploy one terminal per person.
How do I upgrade?
Change the Debian base tag and the ttyd and Node.js versions at the top of services/terminal/Dockerfile and redeploy.
Are there usage restrictions?
Railway's Acceptable Use Policy applies to everything you run. Do not use it for cryptocurrency mining, proxies, anonymizers, torrenting or reselling compute.
Full template README
Deploy and Host Debian 13 Web Terminal with Railway
A Debian 13 (trixie) shell you open in any browser. The shell runs in tmux, so your session and running commands survive closed tabs and dropped connections. A generated password protects it, and your home directory sits on a persistent volume. git, Python, Node.js, build tools and editors come preinstalled.
About Hosting Debian 13 Web Terminal
A web terminal needs a long-running Linux container with a terminal server, real authentication in front of it, TLS, and storage that outlives rebuilds. This community template builds on the official debian:13.7 image and serves the shell with ttyd 1.7.7. nginx stands in front of ttyd and checks a password that Railway generates at deploy. You work as a normal user, debian, with sudo, and /home is a Railway volume. Railway's edge provides HTTPS. Each browser tab attaches to a tmux session, so long jobs keep running after you close the tab.
Common Use Cases
- A Linux shell from a Chromebook, tablet, work laptop or any machine where you cannot install SSH or a VM
- Running long scripts, downloads, builds or bots in tmux and checking back on them later
- Learning Linux commands, apt and shell scripting without a local setup
- Testing scripts, CLIs and packages on Debian 13 before shipping them
- A small always-on scratch box for git, Python and Node.js work
Dependencies for Debian 13 Web Terminal Hosting
- A Railway volume mounted at
/home(included in the template) - Nothing else: no database, no API keys, no external accounts
Deployment Dependencies
- Debian 13 "trixie" release notes: https://www.debian.org/releases/trixie/
- Debian image on Docker Hub: https://hub.docker.com/_/debian
- ttyd (web terminal, MIT): https://github.com/tsl0922/ttyd
- tmux: https://github.com/tmux/tmux/wiki
- nginx basic authentication: https://nginx.org/en/docs/http/ngx_http_auth_basic_module.html
- Railway volumes: https://docs.railway.com/volumes
- Railway Acceptable Use Policy: https://railway.com/legal/fair-use
Implementation Details
| Service | Source | Purpose |
|---|---|---|
| Terminal | Dockerfile based on debian:13.7 |
nginx basic-auth proxy on port 8080 (public HTTPS domain, /healthz), ttyd on loopback, tmux sessions, user debian with sudo, volume at /home |
First login
- Open the service's public URL.
- Your browser asks for a user name and password. The user name is
debian(theUSERNAMEvariable). The password is the generatedPASSWORDvalue on the service's Variables tab. - You land in a tmux session named
main. Close the tab at any time and reopen the URL to resume. For a second, independent session, openhttps://{your-domain}/?arg=work. - Install software with
sudo apt update && sudo apt install {package}. Packages you list in~/.config/debian-terminal/apt-packages(or in theAPT_PACKAGESvariable) are installed again in the background after every redeploy.
What persists: everything under /home/debian: files, dotfiles, shell history, Python virtualenvs, pipx apps in ~/.local, and global npm packages in ~/.npm-global. Running processes and system packages installed with apt reset on every redeploy or restart. tmux keeps sessions alive across browser reconnects, not across container restarts.
Security: the shell is never served without a password. With an empty, short (under 12 characters) or overlong PASSWORD the service still starts, but the login is locked with a random password nobody knows and the deploy log says how to fix it. Invalid PORT, USERNAME or TERMINAL_FONT_SIZE values fall back to the defaults with a warning in the log. nginx checks the password, which the container keeps only as a SHA-512 crypt hash, and rate-limits attempts. It also rejects WebSocket connections from other sites. ttyd listens on 127.0.0.1 only. The password does not appear in logs, process arguments or the shell environment. To change it, edit PASSWORD and redeploy. Browsers cache basic-auth logins until you close them, so use a private window on shared computers.
Scaling: this is a single-user machine on one volume, so keep one replica. Railway scales RAM and CPU vertically up to your plan limit. For a team, deploy one terminal per person.
Pinning and upgrades: the Debian base tag and the ttyd and Node.js versions (with checksums) are pinned at the top of services/terminal/Dockerfile. Change them and redeploy. Every fresh image build runs apt-get upgrade for Debian security fixes. Railway may reuse cached build layers, so bump the base tag (for example to the next 13.x point release) to force a fresh one.
Fair use: Railway's Acceptable Use Policy applies to everything you run in this shell. Do not use it for cryptocurrency mining, proxies, anonymizers, torrenting or reselling compute. Railway may disable resources that break the policy.
Why Deploy Debian 13 Web Terminal on Railway?
Railway gives the terminal an HTTPS URL, a persistent volume and automatic restarts, with no server to administer. You get a protected Debian shell from one click and pay only for the little CPU and memory an idle shell uses.
Guides for this template
View Debian 13 Web Terminal (Browser Shell) on railway.com
Similar templates
| Template | Category | DeploymentsDeploys |
|---|---|---|
| Chatwoot A customer communication platform | Other | 5,871 |
| Ubuntu-Linux Ubuntu terminal accessible via web browser | Other | 4,926 |
| Ubuntu SSH + Claude ARA TM —SSH server with root access + Claude Code pre-installed. | Other | 4,682 |
| Debian-Linux Debian terminal accessible via web browser. | Other | 2,883 |
| Code Server VS Code in the browser | Other | 2,787 |
| Kali Linux (Web Terminal) Instant Kali Linux browser terminal powered by ttyd | Other | 2,632 |