feat(cum-tools): deploy rakazo at bot.cumsek.com #24
Loading…
Reference in a new issue
No description provided.
Delete branch "t3/deploy-rakazo-oci-bot"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
webis published (port 5173); it proxies/apiand/rpcto the API internally.bot.cumsek.comthrough cum-services nginx, with a 16m upload limit and unbuffered responses with a 3600s read timeout for streamed agent output.rakazodatabase on cum-services postgres withcreaterolefor the owner, plus arakazo_applogin (row-level security) with its own pg_hba line.rakazoentry (port, domain, dashboard tile) tocum.nix.rakazo/*secrets on cum-tools andpostgres/rakazoshared with cum-services. Each container gets only the secrets it uses.SANDBOX_SCREEN_NETWORK=internal(bot computers can reach each other) andSANDBOX_COMPUTER_EGRESS=open(no host iptables egress rules exist here).Testing
nix build/nix evalof the cum-tools and cum-services configurations.postgres/rakazo,rakazo/app_db_password,rakazo/better_auth_secret,rakazo/screen_proxy_secret,rakazo/supervisor_token,rakazo/encryption_key.bot.cumsek.comloads, that the API migrations apply on first start, and thatrakazo_appcan connect to therakazodatabase.