Getting Started

Terror Server runs as a single Go binary and is usually installed as a systemd-managed service. The normal production flow is:

1. Install the latest stable release.
2. Edit /etc/terror/Runtime.
3. Validate the config.
4. Let the systemd watcher restart terror.service.
5. Check route health with terror status.

Install

curl -fsSL https://raw.githubusercontent.com/devlopersabbir/terrorserver/main/scripts/install.sh | sudo bash

Then check the service:

terror status

TIP

The installer enables terror.path, a systemd path watcher. Saving /etc/terror/Runtime automatically triggers a service restart so new domains, removed routes, ports, and TLS listeners are picked up.

Your First Runtime

Open the Runtime file:

sudo vim /etc/terror/Runtime

Start with a default static site and one proxied app:

:80 {
    root /var/www/terrorserver
    file_server
}

app.example.com {
    proxy localhost:4000
}

Validate before saving a production change:

terror validate

After saving, confirm the route:

terror status

Mental Model

Each Runtime block has an address and exactly one handler.

Address type	Example	What it matches
Domain	app.example.com	Requests with that hostname
Port	:9090	Any request received on that listener

Each block chooses either proxy or file_server.

api.example.com {
    proxy localhost:3000
}

docs.example.com {
    root /var/www/docs
    file_server
}

Next Steps

• Use Runtime File for all syntax rules.
• Use Reverse Proxy to publish local apps.
• Use Static Sites for frontend builds and simple websites.
• Use HTTPS and Domains before turning on forced redirects.