albion/.env.example
Заид Омар Медхат 337dac78ba
All checks were successful
Deploy / deploy (push) Successful in 3m58s
Client/server split, Postgres, auth, Windows agent, Docker deploy
- Extract world-parse + packet capture into @albion/shared (reused by
  server and a new standalone agent workspace).
- Migrate the data layer from SQLite/better-sqlite3 to shared Postgres
  (async pg with a ?->$n helper; economy engine preloads the item/recipe
  graph so its sync recursion still works).
- API-key auth (ALBION_API_KEY) on all /api routes except health; web UI
  sends it via a fetch wrapper + key-entry gate; server serves the built
  UI with a path-traversal-safe static handler (drops @fastify/static).
- Windows companion agent: pushes world map + captured market orders to
  /api/ingest/*; runs on the gaming PC where the game traffic lives.
- Docker + docker-compose (external proxy + backend networks for Nginx
  Proxy Manager and shared Postgres) and a Forgejo deploy workflow.
- Validated end-to-end against Postgres 16 and a full compose run.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-23 04:10:08 +05:00

10 lines
474 B
Text

# Copy to .env next to docker-compose.yml and fill in.
# Full connection string to your shared Postgres on the `backend` network.
# Use the Postgres container/service name as the host (e.g. `postgres`).
# Create the database first: CREATE DATABASE albion;
DATABASE_URL=postgres://albion:CHANGE_ME@postgres:5432/albion
# Bearer token the web UI and the Windows agent must send. Generate one, e.g.:
# openssl rand -hex 32
ALBION_API_KEY=change-me-to-a-long-random-string