OverCooked Customer Installer
This repository is the public, image-only customer installer. A customer does not need access to any application source repository. The installer downloads only these public images:
git.leee.xin/overcooked/overcooked-egit.leee.xin/overcooked/overcooked-s-controlgit.leee.xin/overcooked/overcooked-s-webuigit.leee.xin/overcooked/overcooked-media-node
It does not download or start an Auth image, and it does not use Docker build contexts.
Install
curl -fsSL \\
https://git.leee.xin/OverCooked/OverCooked-Installer/raw/branch/main/install.sh \\
-o install.sh
sudo env \\
OVERCOOKED_SERVER_IP=203.0.113.10 \\
OVERCOOKED_AUTH_PUBLIC_KEYS='{"auth-1":"PUBLIC_KEY"}' \\
OVERCOOKED_ACTIVATION_CODE='ACTIVATION_CODE' \\
OVERCOOKED_TURNSTILE_SITE_KEY='TURNSTILE_SITE_KEY' \\
OVERCOOKED_TURNSTILE_SECRET_KEY='TURNSTILE_SECRET_KEY' \\
./install.sh
The default central Auth endpoint is http://148.135.97.10:18091. Override it
with OVERCOOKED_AUTH_URL. Auth private keys, administrator credentials,
license databases, provider credentials, and production secrets are never
included in this repository.
The current S production image requires the Turnstile key pair shown above. The installer fails early if the pair is missing or incomplete; it never uses placeholder credentials.
Endpoints
- WebUI:
http://SERVER_IP:18083/ - S API:
http://SERVER_IP:18080/ - E:
http://SERVER_IP:8096/ - First setup:
http://SERVER_IP:18083/setup
The installer checks these host ports before changing service state and does not bind ports 80 or 443. Configure the firewall to allow the chosen public ports and restrict database/Valkey traffic to the Docker networks.
The server address is selected from OVERCOOKED_SERVER_IP, or from the
interface selected by ip -4 route get 1.1.1.1. A detected RFC1918,
loopback, link-local, or carrier-grade NAT address is rejected unless explicitly
provided through OVERCOOKED_SERVER_IP.
Configuration and logs
OVERCOOKED_REGISTRY and OVERCOOKED_VERSION override the default image
registry and tag. OVERCOOKED_ROOT changes the default /opt/overcooked
installation directory. Generated production.env is mode 600 and contains
the setup token and randomly generated service keys. The installer never
prints those values. Keep the file private.
docker compose --env-file /opt/overcooked/production.env \\
-f /opt/overcooked/compose/s.yml -p overcooked-s ps
docker compose --env-file /opt/overcooked/production.env \\
-f /opt/overcooked/compose/e.yml -p overcooked-e logs --tail=100
Migration is fail-closed. E uses the migration command built into its official image. S uses only the schema migration assets published in this repository. If either migration fails, the installer exits non-zero and does not start the corresponding application service.
Common 404/401 download failures
The customer command must fetch the raw script from the public Installer repository. A 404 usually means a wrong repository, branch, or raw path. A 401/403 means that a private source URL or credentialed mirror was used. Do not grant customer access to application source to work around these errors. Use the public raw URL and verify anonymous image pulls instead.
Uninstall
Review the project names and volumes first, then stop the two projects:
docker compose --env-file /opt/overcooked/production.env \\
-f /opt/overcooked/compose/s.yml -p overcooked-s down
docker compose --env-file /opt/overcooked/production.env \\
-f /opt/overcooked/compose/e.yml -p overcooked-e down
The named volumes contain customer data and are intentionally not removed by the installer or this documentation.