Skip to content
This repository has been archived by the owner on Mar 7, 2019. It is now read-only.

don't put help.md into container image #24

Open
TomasTomecek opened this issue Jul 10, 2017 · 2 comments
Open

don't put help.md into container image #24

TomasTomecek opened this issue Jul 10, 2017 · 2 comments

Comments

@TomasTomecek
Copy link
Member

...since help.1 is already in-place

my comment from a former pr:

I would put the `help.md` to `files/` directory and render `help.1` to `root/` directory. WDYT?
@phracek
Copy link
Member

phracek commented Jul 13, 2017

@TomasTomecek What about to render help.1 during container build and copy it to root/ directory? Any reason why to render help.md in container?
I though, files are used for scripts for building/running container.
Does it make sense to create a doc or man directory and put there all files?

Or did I understand wrongly?

@TomasTomecek
Copy link
Member Author

What about to render help.1 during container build and copy it to root/ directory?

That's exactly what I'm proposing. Put help.1 into /root so it ends up inside the image, put help.md into files/ hence it doesn't need to be part of the container image.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants