Feature: Add Dev Container configuration for backend development

[rshaurya]

This PR introduces a VS Code Dev Containers setup to BuffaLogs (#510 ), enabling contributors to spin up a fully configured development environment with minimal local setup.
The goal is to make onboarding easier, reduce environment-related issues, and ensure consistency across contributors’ development setups.

Changes Introduced

Added a .devcontainer/ configuration to the repository.
It includes three files: devcontainer.json, docker-compose.yaml and Dockerfile.dev, all of which are configured for backend development.

Details on how to run and debug using devcontainers can be found in the docs/ folder.

[Lorygold]

@lucaCigarini @eugenioseveri I think that DevContainers could be interesting also for other projects (see also the discussion related to the PR: #510)

Thank you @rshaurya, very nice, I'll test it

[Lorygold]

Hi @rshaurya,
Some notes: only 2 files should be added, one for the backend (.devcontainer/django/devcontainer.json) and the other for the frontend (.devcontainer/node/devcontainer.json). No other files are required (e.g. docker-compose.yaml, because the original one can be used).
Then, the package versions should be fixed and aligned with the libraries and versions in the requirements_dev.txt

[rshaurya]

Some notes: only 2 files should be added, one for the backend (.devcontainer/django/devcontainer.json) and the other for the frontend (.devcontainer/node/devcontainer.json). No other files are required (e.g. docker-compose.yaml, because the original one can be used).
Then, the package versions should be fixed and aligned with the libraries and versions in the requirements_dev.txt

I'm not sure how we can setup a dev container - capable to attaching debugger to any running containers of our choice - in a multi container environment - using just devcontainer.json. Please explain.

And this PR/Issue was specifically for back-end as discussed, I had no plan for front-end, at least in this PR.

I can surely, pin the library versions to align with those in requirements_dev.txt.

[Lorygold]

calling the original docker-compose file, something like this (check the correct path):

{
  "name": "buffalogs_backend",
  "dockerComposeFile": [
        "../../docker-compose.yml"
    ]

doesn't it work?

Ok for the creation only of the backed dev container and thnk for pinning the versions of the libraries as they are in the requirements_dev.txt file, so the env is aligned

[rshaurya]

{
"name": "buffalogs_backend",
"dockerComposeFile": [
"../../docker-compose.yml"
]

No, it won't work. It'll just run the containers as is, with no way to attach a debugger.

And I have updated the library versions.

[rshaurya]

Hi @Lorygold ,
I think all concerns have been addressed, please let me know where we are going with this.

[Lorygold]

Thank you @rshaurya

@Noble-47 any comments about this?