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.

VariableRequiredDescription
SLASHA_PLATFORM_DOMAINYesThe root domain for your instance (e.g., slasha.example.com).
JWT_SECRETYesA long random string used to sign auth tokens. Changing this will log all users out.
SLASHA_ENVNoSet to production for live servers.
SLASHA_PORTNoThe 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, run the install script against the server binary, then restart the service. Your .env and data in /var/lib/slasha are left untouched:

curl -fsSL https://slasha.com/install.sh | sudo SLASHA_INSTALL_DIR=/usr/local/bin bash
sudo systemctl restart slasha

Re-running setup.sh does not upgrade an existing installation — it is only for provisioning a fresh server, and it overwrites /etc/slasha/.env.