Add a Dockerfile and docker-compose for the API, worker, Postgres, and NATS for local/prod parity

[Jagadeeshftw]

📌 Description

The repo deploys via railway.json/.railwayignore and documents Postgres via DOCKER_POSTGRES_SETUP.md, but there is no Dockerfile for the Go service and no docker-compose.yml wiring the API, the worker (cmd/worker), Postgres, and NATS together. Local setup and CI/prod parity rely on ad-hoc steps and make dev (air).

💡 Why it matters: A multi-stage Dockerfile and compose file give reproducible local environments and a clear deployable artifact, reducing "works on my machine" issues.

🧩 Requirements and context

• Add a multi-stage Dockerfile building cmd/api (and a build arg/target for cmd/worker) on the Go 1.24 toolchain, producing a small static image.
• Add docker-compose.yml with services for api, worker, postgres (with a volume), and nats, wired by env.
• Use .env.example as the basis for compose env; ensure /ready is used as a healthcheck.
• Document docker compose up in DEVELOPMENT.md and QUICK_START.md.
• Keep image non-root and minimal.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b devops/dockerfile-and-compose

2. Implement changes

• Write/modify the relevant source: Dockerfile, docker-compose.yml, .dockerignore
• Write comprehensive tests: a CI job that builds the image and runs compose up smoke check (optional)
• Add documentation: DEVELOPMENT.md, QUICK_START.md
• Include comments in the Dockerfile explaining stages
• Validate security assumptions: run as non-root, no secrets baked into the image

3. Test and commit

• Run tests:

docker build -t grainlify-api . && docker compose config

• Cover edge cases: worker target builds; healthcheck hits /ready
• Include build output and security notes in the PR description.

Example commit message

devops: add multi-stage Dockerfile and docker-compose

✅ Acceptance criteria

• Multi-stage Dockerfile builds api and worker
• docker-compose wires api, worker, postgres, nats
• Healthcheck uses /ready
• Local usage documented; image runs as non-root

🔒 Security notes

Do not bake secrets or .env into the image; ensure the final stage is non-root and contains no build toolchain.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[mxrtins04]

Hi, please can i have this issue please?

[retkatmun]

Hi,

I’m a full-stack software engineer with experience building scalable web apps, backend systems,

I’d love to work on this issue. I’ve reviewed the requirements and have a clear implementation plan to deliver a clean, well-tested solution that meets all acceptance criteria and aligns with the project’s standards.

I can start immediately and provide timely updates throughout the implementation.

[Vivian-04]

Hiiiiiiiiii, I would love to work on thissssssss for youuu! I have 3 years of experience with Docker, Go services, CI/CD, and DevOps, and I can build a secure multi-stage container setup with Docker Compose orchestration, non-root images, health checks, and clear local development documentation. ETA: 2-3hours.

Thank you for the consideration.....Thank youuuuuuu!

[grantfox-oss]

🦊 GrantFox — @retkatmun has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #57)
2. Your PR will be reviewed by the Grainlify maintainers

Good luck! Track your progress on GrantFox.