Files
geo/deploy/OFFLINE_PACKAGE.md
T
root 1c19bac8bc
Deployment Config CI / Deployment Config (push) Successful in 24s
Backend CI / Backend (push) Successful in 14m49s
docs(deploy): document pgbouncer rollout
2026-05-03 15:04:17 +08:00

43 lines
1.1 KiB
Markdown

# geo-rankly offline package
This directory is self-contained. It deploys containers, not host binaries.
On a Docker host with Docker Compose v2:
```bash
bash deploy.sh compose
```
`compose` is the default, so this is equivalent:
```bash
bash deploy.sh
```
`deploy.sh compose` loads `images.tar`, creates `.env` from `.env.example` when missing, and starts the stack with:
```bash
docker compose -f docker-compose.yaml -f docker-compose.offline.yaml --env-file .env up -d
```
Runtime services connect to Postgres through PgBouncer in `session` pooling mode. The one-shot `migrate` job still connects directly to `postgres` and `monitoring-postgres` so DDL and seed work do not go through the pooler.
On a k3s host:
```bash
bash deploy.sh k3s
```
This imports `images.tar` into k3s containerd and applies `k3s/` with Kustomize.
Default ports are NAS-friendly:
- tenant web: `18080`
- tenant API: `18081`
- ops web: `18082`
- ops API: `18090`
- RabbitMQ management: `15673`
- MinIO console: `19001`
Edit `.env` before rerunning `bash deploy.sh` if you need real API keys, stronger secrets, or different ports.