-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dockerfile #50
base: main
Are you sure you want to change the base?
Add dockerfile #50
Conversation
Could you rebase on This seems like a good idea, but I have basically no expertise with Docker, so I don't know how to evaluate it. Can you point me at some doco that would get me familiar enough with Docker, Docker Hub, and its interaction with Travis CI so that I could evaluate this? |
Here is the docs: https://docs.docker.com/ |
Okay, I've got a bit of experience with Docker now, and I've cleaned up the spurious failures in Travis CI for real (I think). Would you mind rebasing this on |
@roipoussiere Do you mind to rebase again? |
@@ -0,0 +1,6 @@ | |||
FROM ruby:alpine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my experience, it is not the best way to use such a generic image without any version information. Maybe it is better to use a more concrete image tag.
This PR adds a Dockerfile based on Alpine.
A ronn Dockerfile is useful for Continuous Integration tools (such as GitLab CI), to automatically generate a man page during a build process.
This Dockerfile is currently hosted on Docker hub. If this PR is merged, I can transfer ownship to an other Docker hub user or organization.
Usage
I recommend to use this container with stdin and stdout, in this way we don't have to deal with Docker volumes.
Saving
./my_program.1.ronn
manpage to./my_program.1
:Saving
./my_program.1.ronn
html manpage to./my_program.1.html
:Usage in CI
The image entrypoint must be overridden in your CI tool. For instance, if GitLab CI is used, the
.gitlab-ci.yml
could look like this: