Run your own

What you need#

Install#

1. 1

   Get the code and install

   shellcopy

   cd /opt/obelis
   npm ci

2. 2

   Write the settings

   shellcopy

   npm run setup

   It asks for the domain, the Claude key, the model, the RPC, Privy and the token, makes APP_SECRET and a fresh memo signer wallet, and writes .env.local (an older one is kept as .env.local.bak). Or copy .env.example to .env.local and fill it in.
3. 3

   Check everything

   shellcopy

   npm run doctor

4. 4

   Build

   shellcopy

   npm run build

5. 5

   Run the site and the worker

   Two processes: the site (npm start, port 3000) and the agent (npm run worker). Run exactly one worker. Ready-made units are in deploy/: systemd (obelis-web.service, obelis-worker.service), pm2 (ecosystem.config.cjs) and nginx with HTTPS (nginx.conf), or use Docker.

Every setting#

All settings live in .env.local on the server. Only NEXT_PUBLIC_* values reach the browser, and they are built into the site: change one, then build again. The others are read when the processes start: change one, then restart them.

The site and its links

Sign-in

Solana

The chronicler

Chronicles

Carving

Posting chapters

Token

The optional CA bot

Storage

Privy#

1. 1

   Create an app

   At dashboard.privy.io ↗, create an app. Its App ID is in the app’s settings; put it in NEXT_PUBLIC_PRIVY_APP_ID.
2. 2

   Allow your domain

   In Configuration → App settings → Domains, add your site’s origin exactly as in NEXT_PUBLIC_SITE_URL (https://…). Add http://localhost:3000 too if you test locally.
3. 3

   Turn on the login methods

   In the login methods, turn on Email, X (under socials) and External wallets with Solana. The site asks for exactly these three; one that is off in the dashboard shows “This login option is turned off”.
4. 4

   Solana wallets

   Make sure Solana is on for embedded wallets. The site asks Privy to create one for users who log in with email or X and have no wallet.
5. 5

   Build again

   The App ID is built into the site: npm run build, then restart. npm run doctor checks that it looks right.

Claude#

1. 1

   Get a key

   At console.anthropic.com ↗ → Settings → API keys. Put it in ANTHROPIC_API_KEY on the server.
2. 2

   Add credit and set a limit

   Add credit in Billing, and set a monthly spend limit there too; AGENT_DAILY_USD is the site’s own limit on top of it.
3. 3

   Try one chapter

   npm run agent:test writes one test chapter with your key and settings, and shows its cost. npm run doctor -- --live does it as part of the checks.

What it costs depends on the model, the effort and how much happens: a quiet day costs nothing; a chapter is usually a few cents on Opus, less on Sonnet, a fraction of a cent on Haiku. The agent page shows the real average per chapter once it runs.

The memo signer#

• —npm run setup makes a new wallet for it and writes both MEMO_SIGNER_KEY and MEMO_SIGNER_ADDRESS. Use a wallet that does nothing else.
• —Send it a little SOL (0.05 is plenty). The agent page and /api/health show its balance and warn below MEMO_LOW_SOL.
• —It only ever signs memos. If its key leaked, the worst anyone could do is write memos in its name: make a new one, and the agent page shows the new address.

X#

1. 1

   A developer account

   At developer.x.com ↗, sign in with the account that will post, and create a project and an app.
2. 2

   Read and Write

   In the app’s User authentication settings, set the app permissions to Read and Write (the type can be Web App; the callback and website can be your site’s address).
3. 3

   Keys and tokens

   In Keys and tokens: the API Key and Secret go in X_API_KEY and X_API_SECRET. Then generate the Access Token and Secret (after setting Read and Write, or they will be read-only) and put them in X_ACCESS_TOKEN and X_ACCESS_SECRET.
4. 4

   Restart the worker

   The worker log says “posts to x”. npm run doctor -- --live signs in to X with the keys and names the account that will post.

Telegram#

1. 1

   A bot

   In Telegram, ask @BotFather ↗ for a new bot (/newbot). Its token goes in TELEGRAM_BOT_TOKEN.
2. 2

   A channel

   Create a public channel (or use yours). Add the bot as an administrator with the right to post messages.
3. 3

   Tell the worker

   TELEGRAM_CHANNEL_ID=@your_channel (a private channel: its -100… id). And NEXT_PUBLIC_TELEGRAM_URL=https://t.me/your_channel so the site links it.
4. 4

   Restart

   The worker log says “posts to telegram”. npm run doctor -- --live asks Telegram whether the bot may post in the channel.

Docker#

npm run setup                       # or write .env.local by hand
docker compose up -d --build        # the site on 127.0.0.1:3000 and the worker
docker compose exec web npm run doctor
docker compose logs -f worker

The site and the worker share one volume (/data) with the database and the coin images. The image is built with .env.local as a build secret (the NEXT_PUBLIC_* values are built in); it is not copied into the image. Put nginx or Caddy with HTTPS in front (deploy/nginx.conf).

Checks#

Operating#

• —Back up OBELIS_DATA: the SQLite database (copy it with the site and worker stopped, or live with sqlite3 data/obelis.db ".backup obelis-backup.db") and the coin images next to it.
• —To update: get the new code, npm ci, npm run build, restart both. The database upgrades itself on start.
• —Keep .env.local readable by the service user only (chmod 600). Never put a secret in a NEXT_PUBLIC_ setting.