Ultimately, this devcontainer should be able to replace our existing
Dockerfile/Makefile setup.
Add .devcontainer/Dockerfile. This is similar to our old Dockerfile
but it uses a VSCode devcontainer image as the base. All the same
tools/languages are installed.
Add .devcontainer/devcontainer.json. Forward port 8000 because
that's what the HTTP server runs on.
Add bin/server. This will replace the make server functionality
from our docker entrypoint in the old container.
Before using devcontainers, we had a home-grown solution akin to a
dev container (but not integrated with the IDE) that used a Makefile.
We can delete our old Dockerfile, and update our Makefile to point to
the Dockerfile in our .devcontainer folder. This means:
make test will still work, and we don't need to change our CI.
Anyone who doesn't use VS Code can still run make test, make shell, etc.
Ultimately, this devcontainer should be able to replace our existing Dockerfile/Makefile setup.
.devcontainer/Dockerfile. This is similar to our old Dockerfile but it uses a VSCode devcontainer image as the base. All the same tools/languages are installed..devcontainer/devcontainer.json. Forward port 8000 because that's what the HTTP server runs on.bin/server. This will replace themake serverfunctionality from our docker entrypoint in the old container.Before using devcontainers, we had a home-grown solution akin to a dev container (but not integrated with the IDE) that used a Makefile. We can delete our old Dockerfile, and update our Makefile to point to the Dockerfile in our
.devcontainerfolder. This means:make testwill still work, and we don't need to change our CI.make test,make shell, etc.