Quickstart

This guide walks you from a fresh CLI install to a running application. It takes around five minutes assuming your Slasha server is already up. If it isn't, start withServer Setup.

1. Point the CLI at your server

Tell the CLI where your Slasha server lives. This is saved to your global config and used by all future commands.

slasha set-url https://slasha.example.com

2. Log in

slasha login

You'll be prompted for your email and password. If you are connecting to a fresh server that doesn't have an admin account yet, the CLI will automatically detect this and prompt you to create the initial admin account right in your terminal. Alternatively, you can also create it by visiting the dashboard at https://slasha.example.com.

Your auth token is stored in the system keychain so you stay logged in across sessions. In CI pipelines, set SLASHA_TOKEN as an environment variable instead — see Authentication token for CI.

3. Create an app

slasha create my-app

The name becomes the app's slug — lowercase letters, numbers, and hyphens only. Slasha supports Git authentication via both SSH andHTTPS.

Option A: SSH (Recommended)

To push over SSH, add your public key first:

slasha ssh-keys add ~/.ssh/id_ed25519.pub

Then, add the SSH remote to your local repository:

git remote add slasha git@slasha.example.com:my-app

Note: If running Slasha inside Docker, the SSH server runs on port2222. Your Git remote URL will be: ssh://git@slasha.example.com:2222/my-app.

Option B: HTTPS

Alternatively, push over HTTPS using your Slasha account email and password as credentials. Add the HTTPS remote:

git remote add slasha https://slasha.example.com/my-app.git

5. Link the CLI to your app (optional)

Run slasha link inside your project directory to create a slasha.tomlfile that binds that directory to a specific app. Once linked, every slasha command you run inside that directory automatically targets the right app — no need for the --appflag.

slasha link my-app

The resulting file looks like this:

# slasha.toml
app = "my-app"

6. Deploy your app

Slasha detects either a Dockerfile or auto-builds withRailpack

Push to deploy:

git push slasha main

Slasha starts a build immediately. Watch the deployment progress:

slasha deployments logs

7. Watch your app go live

When the deployment succeeds, your app is live athttps://my-app.slasha.example.com. To verify everything is running:

slasha info

This prints the app status, current deployment, and the URL.

Next steps

Set environment variables — env
Attach a database or cache — services & provision
Add a custom domain — domains
Scale your processes — scale
Back up your SQLite database with Litestream — Litestream Backups