Rework docker container

[n3ph]

As @cfra already mentioned in #24 (comment) we need the docker container to actually enable the user developing juntagrico code.

Proposal 1:

• fork https://github.com/juntagrico/juntagrico to rotebeete
• include https://github.com/rotebeete/juntagrico as a submodule (Devs could set this to feature branch)
• modify docker-compose to build the juntagrico container from source
• tag container with feature branch name from submodule

Proposal 2:

• create PR to move docker code into https://github.com/juntagrico/juntagrico

[cfra]

Proposal 1:

This would allow for nice tracking of juntagrico branches. However, my experience with git submodules thus far has always been that they are cumbersome, annoying and should best be avoided.

Proposal 2:

It might be worthwhile to discuss with upstream if they would be interested to have a docker based development setup.

Right now, it seems they do their development using runserver and sqlite: juntagrico/juntagrico#365 (comment)

Proposal 3:

I don't have a good answer to all of this yet, but in my opinion, it would be useful for a development setup if code could be tested without having to rebuild images and recreate containers for every change.

I pushed a very rough draft of how this could look here: 7a659f2

But I am not 100% sure if this is indeed the way to go, or if other approaches would be better.

Thinking about this a bit more, I believe that directly mounting juntagrico to /home/app/web is not really the right approach:

Depending on our functional requirements, we will not only use the Juntagrico Django app, but also add other apps.

In this scenario juntagrico really is just a package that we are using.

If we want to perform development on the juntagrico package in this setup, then the proper way would probably be to install the juntagrico package in editable mode. 🤔