Run the local core startup workflow. It applies declared S3 buckets and prefixes
idempotently.
make core-up
docker compose \
--env-file compose/projects/core/.env \
-f compose/projects/core/compose.yml \
-f compose/projects/core/compose.dev.yml \
exec redis sh -c 'redis-cli -a "$REDIS_PASSWORD" ping'
To reset only the local pipeline Postgres data:
make core-down
rm -rf compose/.tmp/core/pipeline-postgres
make core-up
Do not use this procedure in production.
Redis Streams are operational event transport. Consumers that need durable
truth should query the schema owned by the pipeline application repository.
Check:
PROD_HOST is reachable.PROD_SSH_PRIVATE_KEY is valid and includes newlines.PROD_SSH_PORT matches the target host.Inspect the target host:
ssh carlos@<PROD_HOST> "docker ps --all"
Then inspect stack logs on the host:
ssh carlos@<PROD_HOST>
cd /srv/<stack>
docker compose logs <service-name> --tail=100
Common causes:
/srv.ssh carlos@<PROD_HOST>
cd /srv/<stack>
docker compose restart <service-name>
Use only when a narrower service restart is insufficient:
ssh carlos@<PROD_HOST>
cd /srv/<stack>
docker compose down
docker compose up -d