Server Configuration

Configure your Slasha platform through a single .env file.

Environment Variables

Your server’s core settings live in /etc/slasha/.env. After modifying this file, you must restart the Slasha service to apply the changes.

Variable	Required	Description
`SLASHA_PLATFORM_DOMAIN`	Yes	The root domain for your instance (e.g., `slasha.example.com`).
`JWT_SECRET`	Yes	A long random string used to sign auth tokens. Changing this will log all users out.
`SLASHA_ENV`	No	Set to `production` for live servers.
`SLASHA_PORT`	No	The internal port Slasha listens on (defaults to `3000`).

Managing the Service

Slasha runs as a systemd service. Use these commands to manage your platform:

# Check platform status
sudo systemctl status slasha

# View live platform logs
sudo journalctl -u slasha -f

# Restart the service (required after .env changes)
sudo systemctl restart slasha

Data & Backups

Slasha stores its internal state (database, Git repos, and logs) in /var/lib/slasha. Backing up this single directory is enough to save your entire platform configuration.

Note: Application data is stored in separate Docker volumes. See the Storage Guide for more details.

Upgrading

To upgrade to the latest version, re-run the setup script. It will download the new binary and restart the service for you:

curl -fsSL https://your-domain.com/setup.sh | bash