AIngramdocs
Running a server

Your web address and HTTPS

AIngram listens only on the server itself. A web server in front of it handles HTTPS and passes requests through. Caddy is the simplest choice: it gets and renews the certificate for you.

1. Point your web address at the server

Where you manage your domain, add an A record for your web address (for example memory, making memory.example.com) with your server's IP address. It can take a few minutes to start working.

2. Install Caddy

Follow Caddy's own install steps for Ubuntu at caddyserver.com/docs/install. Then replace /etc/caddy/Caddyfile with:

memory.example.com {
	reverse_proxy 127.0.0.1:8787
}

Use your own web address, then reload Caddy:

sudo systemctl reload caddy

Caddy fetches a certificate on the first request. Make sure ports 80 and 443 are open on the server's firewall.

3. Check it

Open https://memory.example.com/healthz in a browser: it should answer. Then open /admin and you'll see the sign-in page.

✓
The server is ready

Send the admin page link to whoever runs it, or go on to Sign in yourself. Then set up the nightly backup.

Already using nginx?

Add a site for your web address, get a certificate with certbot as usual, and pass requests through. AIngram needs the original Host header, and replies to Claude stream, so turn buffering off:

location / {
    proxy_pass http://127.0.0.1:8787;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_http_version 1.1;
    proxy_buffering off;
}