docker: add production compose override for localhost-only ports

[cfsmp3]

Summary

• Adds production/docker-compose.production.yml that binds all service ports to localhost only
• Updates production/README.md to use the override file instead of manual editing
• Adds useful production commands (logs, restart, rebuild)

Changes

New file: production/docker-compose.production.yml

Uses !override YAML tag to replace port arrays (not merge them). Requires Docker Compose v2.24.0+.

Service	Development	Production (with override)
frontend	80:80	127.0.0.1:3000:80
backend	8000:8000	127.0.0.1:8000:8000
syncserver	8080:8080	127.0.0.1:8081:8080

Usage:

docker compose -f docker-compose.yml -f production/docker-compose.production.yml up -d

Why

• Keeps the base docker-compose.yml unchanged for development
• Provides a versioned production configuration (no more manual edits on VPS)
• Makes it easier to update VPS by just pulling changes

Test plan

• Verify override file syntax is valid: docker compose -f docker-compose.yml -f production/docker-compose.production.yml config
• Test on VPS: ports should only be accessible from localhost after applying override
• Verify frontend accessible via nginx (https://taskwarrior-server.ccextractor.org/) - 200 OK
• Verify backend health endpoint (https://taskwarrior-server.ccextractor.org/health) - 200 OK
• Verify sync server (https://taskwarrior-server.ccextractor.org/taskchampion/) - 200 OK
• Verify direct port access blocked (ports 3000, 8000 - connection refused)

Note: Initially tried !reset but it clears arrays without applying new values. !override works correctly.

🤖 Generated with Claude Code

[github-actions]

Thank you for opening this PR!

Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools.

Please take a moment to:

• Check the "Files changed" tab
• Leave comments on any lines for functions, comments, etc. that are important, non-obvious, or may need attention
• Clarify decisions you made or areas you might be unsure about and/or any future updates being considered.
• Finally, submit all the comments!

More information on how to conduct a self review:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request

This helps make the review process smoother and gives us a clearer understanding of your thought process.

Once you've added your self-review, we'll continue from our side. Thank you!