Improving documentation - how to provide config.yaml or modify default config

[agilityprop]

Hi, one thing I found a bit challenging when implementing this container was exactly how to provide my own config.yaml or modify the default one - mostly as I'm not too familiar with using docker volumes and where these things are stored/how to work with them. Are you open to me submitting a paragraph or two describing how to do this in practical terms for inclusion in the documentation? If yes, is that done via a pull request?

[11notes]

Are you open to me submitting a paragraph or two describing how to do this in practical terms for inclusion in the documentation?

I’m open for education, issue is it does not belong on the image README.md itself. It would fit better on a repo with manuals that explains things, but then again, how to use volumes is explained over and over again all over the internet. Adding educational content to each container image I maintain is not something I want to do, because the images are just that, images. They are not meant to educate. What I can think of is to make the manual repo, create the manual with an example container and then add a link for each container that has a volume in the project.md to automatically be added to it so people can click link if they need to know how to provide their own config.

[agilityprop]

That sounds like a very sound approach that considers more than just the one container I had in mind - but probably a low priority... after all even though relatively inexperienced, I was able to muddle through with a bit of googling and get it how I intended after a few tries. Best, AP