[FEATURE] backend: Add Dev Container configuration for local development

[rshaurya]

Feature request for developers - devcontainer specification in repository can help developers launch this on VS Code or other IDE and services build and running. It can setup pre-commit hooks and all linters in one go.

This can really help first time contributors like me :)

During my own setup, I found that using a Dev Container significantly reduced this problem and allowed me to get a fully working development environment with little to none manual configuration.

I propose adding a Dev Container configuration (i.e., a .devcontainer/ directory with devcontainer.json file) to the repository.

This would allow contributors to:

• Open the project in VS Code with the Dev Containers extension
• Automatically build and start the required services
• Reduce errors in initial setup
• Enable access to a development environment
• Begin development immediately in an isolated environment
• Have pre-commit hooks and linters all setup.

This can reduce setup issues, and ensure environment consistency across contributors.

Additional context

This feature is optional so developers who prefer manual setups can continue using it as-is, while new contributors can benefit from a faster

Happy to submit a PR if this change is acceptable.

[Lorygold]

Do you think these is really useful? How this will simplify the process? Isn't it necessary to tag the dev containers?

[rshaurya]

Yes, I do think this is useful. The process is really simple and convenient for anyone having the Dev Container extension installed.

The dev container spins up and stops all container services on its own. This just helps first timers to run and experiment with the code easily. Also anyone can use this setup by installing the Dev Container extension, so tagging the dev containers is not needed.

I have attached a screencast demonstrating the functionality.

Screencast.from.2026-01-03.11-47-25.1.mp4

I'd appreciate your thoughts.

[Lorygold]

Running docker compose up -d returns the same result, isn't it?

[nishantxscooby]

You’re right that docker compose up -d brings up the same services.
The devcontainer doesn’t replace compose — it wraps it with a reproducible dev environment layer.

What it adds beyond compose:

Pins Python / Node / tooling versions so contributors don’t fight local setup issues.

Auto-installs linters, formatters, pre-commit hooks and VS Code extensions.

Attaches the editor directly into the backend container with correct paths, env vars and debugging preconfigured.

Enables true “open and code” onboarding for first-time contributors.

I can prepare a minimal .devcontainer/ using the existing docker-compose.yml so there is zero behavior change for current users — it would be fully optional.

If you’re okay with that direction, I’ll open a PR with:

.devcontainer/devcontainer.json referencing existing compose services

basic toolchain pinning

no changes to production workflows

[rshaurya]

Completely agree with @nishantxscooby !

I'd like to add one more angle that I was thinking about: debugging support.
My primary objective was: debugging support for services and tests. This setup along with few vs code settings, allows me to attach/run debugger with Django app, celery jobs and even tests. Having break-point support for the stack—including background tasks and tests, really help developers to understand and work with complex code.

@nishantxscooby covered the environment consistency benefits nicely. I see the debugging capabilities as an addition to that, making the dev experience both consistent and powerful.

[Lorygold]

Thanks for your valuable clarifications! @rshaurya feel free to proceed with the PR.

Please, update also the dev guide doc

[rshaurya]

Hi @Lorygold !

I've opened the PR for this feature.

[nishantxscooby]

@Lorygold Hi, Can I start working on this?