In some cases, it may be valuable to run the DNS server in a Docker container, such as if it is being run within Kubernetes or a repeatable build is needed without having to install Go build tools on the server. I personally am running ztDNS in a Docker container with a restart policy of Always, so I can keep the server running yet separate from existing system processes.
This PR adds the following:
Dockerfile for building ztdns and running the server
docker-compose.yml for running the built image
gitignore and dockerignore files
It also moves the default .ztdns.toml to .ztdns.toml.example as the former is going to be modified by the user when using the Docker build, and it should not be committed to git.
Let me know if there's anything in the documentation that is unclear, or the Docker build does not work as expected.
In some cases, it may be valuable to run the DNS server in a Docker container, such as if it is being run within Kubernetes or a repeatable build is needed without having to install Go build tools on the server. I personally am running ztDNS in a Docker container with a restart policy of Always, so I can keep the server running yet separate from existing system processes.
This PR adds the following:
It also moves the default
.ztdns.toml
to.ztdns.toml.example
as the former is going to be modified by the user when using the Docker build, and it should not be committed to git.Let me know if there's anything in the documentation that is unclear, or the Docker build does not work as expected.