Files
EvoBGP/deploy/compose/docker-compose.microvps-full.yaml
T
DenozordecandCursor 8267141136
CI / changes (push) Successful in 5s
CI / commitlint (push) Skipped
CI / openapi (push) Successful in 38s
CI / web (push) Successful in 55s
CI / go (push) Successful in 1m4s
CI / bird2 (push) Successful in 17s
CI / release (push) Successful in 4m17s
ci(gitea): point registry and remotes at git.shx.one
Перевести CI, semantic-release, bake и compose с git.shts.su на git.shx.one.

Co-authored-by: Cursor <[email protected]>
2026-08-17 16:43:39 +07:00

69 lines
2.0 KiB
YAML

# Дополнительный файл Compose: профиль microvps-full + ужатые лимиты под хост ~1 ГиБ RAM.
#
# Запуск (PowerShell, из каталога deploy\compose): сначала .env из .env.example, docker login git.shx.one, docker compose pull
# docker compose -f docker-compose.yaml -f docker-compose.microvps-full.yaml --profile microvps-full up -d
#
# Остановка:
# docker compose -f docker-compose.yaml -f docker-compose.microvps-full.yaml --profile microvps-full down
#
# Лимиты под хост ~1 ГиБ: сумма лимитов контейнеров ~800 МиБ + запас ОС/Docker. При OOM увеличьте RAM VPS или уберите prometheus/nats из профиля (отдельная правка compose).
# Postgres ниже ~240–256 МиБ часто не успевает пройти healthcheck / падает по памяти — не уменьшайте postgres без tuned postgresql.conf.
services:
evobgp-all:
environment:
EVOBGP_BROKER_URL: nats://nats:4222
EVOBGP_SERVICE: evobgp-all
EVOBGP_RUNTIME_LOGS_DIR: /opt/evobgp/runtime-logs
volumes:
- type: bind
source: ${EVOBGP_RUNTIME_LOGS_HOST_DIR:-./runtime-logs}
target: /opt/evobgp/runtime-logs
bind:
create_host_path: true
deploy:
resources:
limits:
cpus: "0.85"
memory: 280M
postgres:
deploy:
resources:
limits:
cpus: "0.45"
memory: 256M
bird2:
deploy:
resources:
limits:
memory: 96M
evobgp-agent:
deploy:
resources:
limits:
memory: 48M
nats:
deploy:
resources:
limits:
cpus: "0.2"
memory: 48M
evobgp-web-microvps:
deploy:
resources:
limits:
cpus: "0.3"
memory: 48M
prometheus-microvps:
deploy:
resources:
limits:
cpus: "0.25"
memory: 128M