3 ms·
What I expect is a list of dependencies I can install myself, instructions to compile the code, and a description of config files to write/edit, eg. to point th
by progval 3y ago
What I expect is a list of dependencies I can install myself, instructions to compile the code, and a description of config files to write/edit, eg. to point the main software to its dependencies' URLs. Like this, for example: https://docs.joinmastodon.org/admin/install/ https://docs.joinmastodon.org/admin/install/
- TeMPOraL 3y agoSo basically, you want a Dockerfile.
- zaptheimpaler 3y agoYes this is called a Dockerfile. Better yet, its not just a list, its working code so you don't have to run through the list manually.
- progval 3y agoWhile a readable Dockerfile can work as documentation, there are a few caveats: * the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image. * I still need a way to be notified of updates; if the Dockerfile just wgets a binary, this doesn't help me. * The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-images https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)