Before installing
Bring a server and a domain. Telebugs guides you from the first prompt to a working HTTPS app. Here’s what to have ready before you start.
A little preparation. Then one command
You don’t need to assemble a database cluster or learn a deployment platform. Telebugs runs in one Docker container, with SQLite built in. For the standard installation, have these three things ready:
- A Linux server you can reach over SSH, with permission to install software.
- A domain or subdomain pointing directly to that server, with DNS proxying turned off.
- Ports 80 and 443 open for HTTPS setup and certificate renewal.
A small VPS is enough to get started: 1 CPU core, 1 GB of RAM, and 40 GB of disk. Busier apps need more room. The small-server walkthrough shows what we tested and what affects capacity.
The installer takes it from there
After buying Self-hosted, you receive a private installation command by email. Run it on your server. It asks for your domain, installs Docker if needed on supported Linux systems, configures HTTPS, and starts Telebugs. Progress appears in the terminal. When it’s ready, you get the address of your running app.
Open that address, create your first user and project, and connect your app. Watch the installer at work, or follow the installation manual when you’re ready to run it yourself.
Using an internal network or your own reverse proxy? The manual covers custom setup, too. Your team and every reporting app still need to reach and trust the Telebugs address, including browsers running outside your network.
An easy install is only the beginning
New installations check for app updates each day. You can change the schedule or update manually. Built-in backup tools package and verify the databases, artifacts, configuration, and recovery secrets. A backup stops the app while it creates a consistent archive, so allow a maintenance window as your data grows.
You still look after the server: host security, disk space, email delivery, and an encrypted backup kept somewhere else. Set retention early. Test a restore on an isolated host with production notification destinations blocked; restored jobs must not send real alerts. The backup and restore runbook has the exact procedure. App updates don’t create a backup for you.
Send one error before sending all of them
Connect a staging app first. Open its report, check the backtrace and captured data, and trigger the notification you intend to use. Test a background job or browser error if your app has those, too. That tells you much more than a running container does.
Want Telebugs without owning that server work? Choose Managed and we’ll set up your private instance and handle updates, backups, and upkeep. If running your own software is the point, Self-hosted gives you that control with help directly from the person building it.