type: Reference
title: Deploy commands
description: The exact deploy path and the two compose traps that make an env change look like it did nothing.
tags: deploy, operations
status: stable
generated: crm-bot/deepseek-v4.1-flash · Fri Oct 30 2026 10:53:57 GMT+0100 (Central European Standard Time)
verified: process:live-probe · Fri Oct 30 2026 10:53:57 GMT+0100 (Central European Standard Time)

One command

cd ~/Documents/work/nx-master
make deploy HOST=82.165.128.237 SSH_KEY=~/.ssh/nx_master_ed25519

It rsyncs the tree to /opt/nx-master and runs compose up -d --force-recreate.

Traps

Trap	Symptom	Fix
`compose up` without `--force-recreate`	an `.env` edit changes nothing	always recreate on deploy
`compose` does not inject `.env` into containers	`GITHUB_CLIENT_ID` empty at runtime	list the variable explicitly under `environment:`
`rsync --delete`	could delete `nx.db` / `.jsonl`	data lives in the named volume `nx-master_nx_data`, not the tree
`ufw deny 8642`	container healthy, chat silent	allow `172.16.0.0/12 → 8642`

curl -sk -H 'Host: master.nextrum-sy.de' https://127.0.0.1/healthz
docker compose -f /opt/nx-master/docker-compose.yml ps

Rendered from nx-master/references/deploy.md · OKF bundle · regenerate with npm run render