Config only volume

[redNixon]

create VOLUMEs only on the configuration/storage parts of MISP config. Too complicated, but would like advise on the how-to if someone knows

I did some (limited)testing of this PR(harvard-itsecurity/docker-misp#17) from harvard-itsecurity misp container project and seemed to work pretty well. This seems like the right approach but I am not a fan of how that project builds the image or how everything is all running in a singular container at the end(and the main repo is still on 16.04).

Since you forked 7 month ago, have any opinions on if it is worth implementing this vs just accepting that the VM route is better long term? Based on the numbers of hours that I've already spent on this, the layout and coding style of MISP is making the idea of containerizing it cleanly seem questionable.