cyberia/projects/events/deploy.md

Cyber Valley Tickets Deployment

Deployment is now intentionally split into 3 simple operations.

1) One-time system setup

Runs all root/system-level setup in one place:

  • user/directories
  • packages (postgres, caddy, podman, cache)
  • systemd unit installation
  • caddy site config
  • ipfs/ganache containers
  • /etc/env/tickets.env generation from deploy/.env
cd deploy
make setup-system

2) Backend deploy

Single script for backend updates:

  • rsync backend code + ethereum artifacts
  • refresh /etc/env/tickets.env
  • uv sync
  • migrations
  • restart backend services (tickets-backend, tickets-indexer, tickets-telegram)
cd deploy
make deploy-backend

3) Frontend deploy

Local build + rsync only:

cd deploy
make deploy-frontend

Combined deploy

cd deploy
make deploy-all

Ops commands

cd deploy
make status
make logs
make logs-backend
make logs-indexer
make logs-telegram

Required local config

Create deploy/.env from deploy/.env.example and fill required values.

cd deploy
cp .env.example .env

Folder

Homonyms

soft3/deploy
deploy
warriors/trisha/roadmap/deploy
Neptune deployment preparation `trisha deploy --dry-run` retains explicit offline program inspection. A program execution proof alone does not establish Neptune transaction validity. The dedicated `trisha-neptune` crate owns canonical Neptune0.15.1 transaction and RPC types pinned to…
warriors/trisha/cli/deploy
deploy
neural/trident/src/deploy
deploy
cyberia/projects/mimi/deploy
deploy

Graph