Container Image for Nullboard

[localleon]

Hey,

thanks for your great work.

This PR adds a simplistic Dockerfile to build an container image with nullboard installed. It contains a minimal nginx install and the nullboard files.

Hope this helps! If you're interested we could publish this image via the Github Container Registry

[localleon]

I've just gone ahead and added an Github Workflow file. This file will build a new docker image on every push on master.

Container images can then be downloaded under the [Package Section](https://github.com/localleon/nullboard/pkgs/container/nullboard the) following packages. (the image currently is uploaded to my fork, the file will create a new container registry under your profile without any manual actions required)

docker pull ghcr.io/localleon/nullboard:master

For more information hit me up or see:

• https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry
• https://github.blog/2021-06-21-github-packages-container-registry-generally-available/
• https://www.cloudsavvyit.com/7138/how-to-set-up-automatic-builds-for-docker-images-on-github/

[apankrat]

Hi Leon,

Thanks for the PR.

Here's the deal. I have no need for this personally and as such I don't want to take on responsibility for maintaining and supporting this in a long run, which is something that will have to do if I were to merge this PR in.

The alternative option is to have this live in a fork, managed by you or someone else, and then have main Readme link to it.

Here's where it gets interesting - we tried this exact arrangement before and the fork is now 65 commits behind the origin. I have no problem giving it another try, i.e. repointing the link at another fork, but the assumption will obviously be that Dockerization support will be under your supervision (obviously, with no strings attached and while you are interested in chipping in this way).

Let me know what your thoughts are.

Regards, Alex

[localleon]

Hi apankrat,

thanks for your answer. These are some very important things to think about.

Github actions mostly take away alll the work from the maintainer. But still, someone needs to pdate the dockerfile once in a while to a new verison. I personally belive that docker images make projects much eaisier to try out and test.

II don't think this feature would warrant a fork. It doesn't offer enough added value for that. That's why I would close this PR.