Dockerization of deployment

having access to deployment-repo , i thought right now, "good, so i can test 'somewhen myself",.. but without access to API submodules, locally this is not possible.

So I had the IDEA, to use something like that:

docker-compose.yml

 api-endpoint:  stage.botc.org
 api-port: 80

docker-compose.yml.local

 api-endpoint:  localhost
 api-port:   8081      #example

i guess this switch could be made with environment variables too, but switching the docker-compose.yml file may be the easiest way...

so we could achieve:

a) new frontend devs can develop via docker

further on

b) full devs can hack on the complete system with api

didnt thought about this setup now awfully a lot, it may also be easier to have two different docker-setups, 'botc.docker.backend' and 'botc.docker.frontend', maybe merging them into 'botc.docker' for full development.

surely, this needs more thoughts, but i could see some benefits in a split (local docker for frontend-dev against API would also give hobbyist a helping hand to develop against their own BOTC wallet...).

if this sounds reasonable, i would dive into it a bit more :)