llms.txt
Compare with other sites' llms.txt files →# Chasen
> Chasen is a free, open-source (Apache 2.0) CLI that deploys the Docker image of an app with a SQLite database to one server you own. It gives HTTPS, deploys without downtime, custom domains, hourly checked backups, and a live replica of each SQLite database to S3-compatible storage, about a second behind. `chasen deploy` builds the image on your computer or in CI and sends it to the server through SSH: no registry, no token, and nothing builds on the server.
Who it is for: one person or a small team with one server and many small apps, each with its data in SQLite. Not for: apps that need several servers or Postgres (use Kamal for that).
## Install and first deploy
```bash
curl -fsSL https://chasenhq.com/cli | sh
cd myapp
chasen deploy --server root@203.0.113.5 --domain myapp.example.com
```
The first deploy installs Chasen on the server through SSH (and Docker when the server has none). After that, `chasen deploy` in the directory of the app deploys again. The server needs Ubuntu or Debian, SSH, ports 80 and 443 open, and a DNS record for the domain of the app. The computer needs Docker and git.
An app that someone else releases as an image deploys from any directory. `--auto-update` deploys the newest image of the tag each night:
```bash
chasen deploy ghcr.io/acme/chat --domain chat.example.com --auto-update
```
## The app standard
An app that follows four rules needs no configuration:
1. A Dockerfile, built on your computer for the CPU of the server. A static website with an `index.html` needs none.
2. It serves HTTP on one port: the one the image declares with EXPOSE, or `$PORT`.
3. `GET /up` returns 200, so Chasen knows the new version works before it gets traffic.
4. It keeps its SQLite files in `/storage`, or in the VOLUME the image declares.
`chasen.yml` in the directory of the app holds only what differs: another port or health path, env, secrets, cron jobs, a jobs container, memory. It is not a docker-compose file: an unknown key is an error. Chasen gives every app `PORT`, `BASE_URL`, `SECRET_KEY_BASE` (also `PRIVATE_KEY`), `STORAGE_DIR`, `DATABASE_PATH`, `APP_VERSION`, and `APP_ENV`.
## Commands
- `chasen deploy`: build and deploy the app of this directory. `--tag <version>` deploys an existing image.
- `chasen status`, `chasen logs`, `chasen history`: what runs, its output, and every past deploy.
- `chasen rollback`: back to the version before, in seconds. The server keeps the last 5 images.
- `chasen backup`, `chasen backups`, `chasen restore`, `chasen verify`, `chasen download`: backups and the proof that they restore.
- `chasen bucket`: send backups and the live replica to S3-compatible storage.
- `chasen secrets edit`: secrets encrypted in `chasen.secrets.enc`, like Rails credentials.
- `chasen run <command>`: one command in the container. `chasen ssh`: a shell in the container.
- `chasen alerts`: what is wrong with the server or puts it at risk, each with its fix.
- `chasen` with no command: a live screen of the server, its apps, history, backups, domains, and logs.
- Chasen for Mac (https://chasenhq.com/mac/): the servers in the menu bar, and the screen as a window. It reads, and the CLI changes.
- `-a <app>` picks the app, `--server <user>@<host>` picks the server.
## Backups
A checked snapshot of every SQLite database each hour and before each deploy, kept 24 hours, 7 days, 4 weeks, and 6 months. With a bucket, a live replica (Litestream, inside Chasen) copies each change about a second behind. A restore is one command. A server without a bucket is complete: the snapshots stay on its disk.
## On the server
Chasen puts one program on the server, `chasen-server`, in a container with the Docker socket. It runs the proxy (kamal-proxy, with HTTPS from Let's Encrypt), the backups, the live replica, the history, and the alerts, and it updates itself each night. It does not harden the server or change the operating system: that stays the owner's.
Pricing and license: free. Apache 2.0, source on GitHub. Made by Carlos Castellanos (@karloscodes, https://karloscodes.com).
## Docs
- [Get started](https://chasenhq.com/docs/): from an empty server to a live app.
- [Deploy](https://chasenhq.com/docs/deploy/): the image, websites, images that others release, `chasen.yml`, and the review before each deploy.
- [The app standard](https://chasenhq.com/docs/standard/): the port, `/up`, the storage, migrations, and the env Chasen sets.
- [Backups and restore](https://chasenhq.com/docs/backups/): snapshots, the live replica, a restore, and a new server.
- [Secrets](https://chasenhq.com/docs/secrets/): `chasen secrets edit` and the key.
- [Domains](https://chasenhq.com/docs/domains/): custom domains, and Cloudflare in front.
- [Deploy from GitHub Actions](https://chasenhq.com/docs/github-actions/): `git push` as the deploy.
- [Commands, files, and limits](https://chasenhq.com/docs/reference/): every command, the files on the server, and what Chasen does not do.
- [The protocol](https://chasenhq.com/docs/protocol/): the HTTP API between the CLI and the server.
- [Omarchy](https://chasenhq.com/docs/omarchy/): the screen in your theme, and a status bar module.
## Source
- [GitHub repository](https://github.com/karloscodes/chasen): source (Apache 2.0), issues, and releases.
- [How it works](https://chasenhq.com/how-it-works/): the CLI, the server program, and the path of a deploy.
- [Stats](https://chasenhq.com/stats/): download counts, releases, and GitHub metrics.