Sipp

Minimal code sharing

Features

• Single binary for web server and TUI
• Create snippets and share on the web
• Raw output for CLI tools — curl, wget, and httpie get plain text automatically
• Interactive TUI with authenticated access for snippet management
• Minimal, fast, and low memory consumption

Quickstart

1. Install

Install via the releases page, or directly with cargo

cargo install sipp-so

To confirm it was installed correctly run the following

sipp --help

2. Start Server

For demo purposes you can run this locally, but ideally this would be run in a deployment server with a proper ENV setup with your admin key.

sipp server --port 3000

3. Create a Snippet

You can either open up http://localhost:3000 and create a snippet in a web browser, or use the TUI. In the same directory, open a new terminal window and use

# Path to file
sipp path/to/file.rs

# Or use the interactive tui 
sipp

Demo Instance

A small instance running at sipp.so that can be used for testing and demo purposes.

sipp -r https://sipp.so

[!WARNING] All snippets created here are public and might be deleted at any time; host your own instance with your own API key for personal use!

Install

Sipp can be installed several ways

Releases

Visit the releases page and install through cURL script and other methods.

Homebrew

brew install stevedylandev/tap/sipp-so

Cargo

cargo install sipp-so

Usage

CLI

sipp [OPTIONS] [FILE] [COMMAND]

Commands

Arguments

Options

Server

Sipp includes a built-in web server powered by Axum. Start it with:

sipp server --port 3000 --host localhost

Environment Variables

The server stores snippets in a local sipp.sqlite SQLite database.

API Endpoints

Authenticated endpoints require an x-api-key header.

Raw Output for CLI Tools

When you access a snippet URL (/s/{short_id}) with curl, wget, or httpie, the server returns the raw content as plain text instead of HTML:

curl https://sipp.so/s/abc123

TUI

The Sipp TUI makes it easy to create, copy, share, and manage your snippets either locally or remotely. Launch it with:

# Launch TUI (default behavior when no file argument is given)
sipp

# Or explicitly
sipp tui

# With remote options
sipp -r https://sipp.so -k your-api-key

Local Access

If you are running sipp in the same directory as the sipp.sqlite file created by the server instance, the TUI will automatically access the datebase locally and you can edit it directly.

Remote Access

To access a remote instance of Sipp make sure to do the following:

• Set the SIPP_API_KEY variable in your server instance
• Run sipp auth to enter in your server instance URL and the API key, which will be stored under $HOME/.config/sipp. You can also set these with the ENV variables SIPP_REMOTE_URL and SIPP_API_KEY

[!NOTE] You can try a limited remote instance without an API key with sipp -r https://sipp.so

Actions

While inside the TUI the following actions are available

Deployment

Since Sipp is a single binary it can be run in virtually any enviornment.

Systemd

Create a service file at /etc/systemd/system/sipp.service:

[Unit]
Description=Sipp snippet server
After=network.target

[Service]
ExecStart=/usr/local/bin/sipp server --port 3000 --host 0.0.0.0
Environment=SIPP_API_KEY=your-secret-key
WorkingDirectory=/var/lib/sipp
Restart=on-failure

[Install]
WantedBy=multi-user.target

sudo systemctl enable --now sipp

Docker

A Dockerfile and docker-compose.yml are included in the repository.

# Using Docker Compose (recommended)
SIPP_API_KEY=your-secret-key docker compose up -d

# Or build and run manually
docker build -t sipp .
docker run -p 3000:3000 -e SIPP_API_KEY=your-secret-key -v sipp-data:/data sipp

Railway

1. Fork this repo and connect your fork to Railway
2. Set the environment variables SIPP_API_KEY and optionally SIPP_AUTH_ENDPOINTS
3. Add a volume to your service and mount it at /data
4. Set SIPP_DB_PATH to /data/sipp.sqlite so the database persists across deploys