It seems like the config.ini is being built into the image. Is there a way to have this run through a persistent volume and running -v during docker run?
It seems like the config.ini is being built into the image. Is there a way to have this run through a persistent volume and running -v during docker run?
<!-- github-sync-id:2776718082 -->
Yea likely can sort it out soon. Did you see the new code @turnrye enhanced in the alpha branch? It would be cool to get some testing feedback.
There is a new docker in the "alpha " lab copy git checkout lab from the project home
Yea likely can sort it out soon. Did you see the new code @turnrye enhanced in the alpha branch? It would be cool to get some testing feedback.
There is a new docker in the "alpha " lab copy `git checkout lab` from the project home
<!-- github-comment-id:2579165488 -->
while not persistent I did add some tools to make this easy from windows. https://github.com/SpudGunMan/meshing-around/blob/main/script/docker/README.md
<!-- github-comment-id:2585930606 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It seems like the config.ini is being built into the image. Is there a way to have this run through a persistent volume and running -v during docker run?
Yea likely can sort it out soon. Did you see the new code @turnrye enhanced in the alpha branch? It would be cool to get some testing feedback.
There is a new docker in the "alpha " lab copy
git checkout labfrom the project homeI put a config.ini editor script into the new alpha branch
while not persistent I did add some tools to make this easy from windows. https://github.com/SpudGunMan/meshing-around/blob/main/script/docker/README.md