Octoprint volumes are problematic

[MatthewCroughan]

Octoprint volumes are problematic

[MatthewCroughan]

This PR #11 is a Change-type: major due to this issue. If we can have our own /usr/src/octobalena/config.yaml and combine it with the one that Octoprint is managing at runtime, then we can solve this. Until then, we cannot change the config.yaml without it being a major change.

[MatthewCroughan]

Regarding plugins, I noted the following in #10

to get around this for the time being I use PYTHONUSERBASE=/usr/local in the Dockerfile, so that plugins installed by the Dockerfile are stateless and installed in an unmanaged directory.

/data/plugins should remain a managed directory since then user installed plugins remain, obviously. The only real issue is that we cannot change portions of the config.yml for a user after they've installed Octobalena, so any major changes will not propagate to them.

[thzinc]

I think my PR #41 might have resolved some of the symptoms described here by updating the --basedir to be a path under /data.