This PR adds a Dev Container which can be used to work on the codebase more easily, through VS Code (via the Remote-Containers extension) or GitHub Codespaces.
Because imaginary needs some libraries installed, setting them up–and having the right versions–on a development machine can be a pain. Using a dev container removes the problem and allows working on imaginary quickly and without messing up with the host.
The dev container is based on the official containers for Go 1.17 and it includes the libraries that imaginary needs as per the Dockerfile (both dev and runtime). Note that this used Debian Bullseye as base, so see also #384.
This PR adds a Dev Container which can be used to work on the codebase more easily, through VS Code (via the Remote-Containers extension) or GitHub Codespaces.
Because imaginary needs some libraries installed, setting them up–and having the right versions–on a development machine can be a pain. Using a dev container removes the problem and allows working on imaginary quickly and without messing up with the host.
The dev container is based on the official containers for Go 1.17 and it includes the libraries that imaginary needs as per the Dockerfile (both dev and runtime). Note that this used Debian Bullseye as base, so see also #384.