[GNPIP] Add geonode-project CLI with docker subcommand

[francbartoli]

Proposal

Currently we have got rid of mounting docker socket and the deployment cannot automagically discover ip address of the daemon along all the possible cases (Docker4Mac, Docker Machine, Native Linux, etc).
The aim of this command line is to give the users an utility to ease the configuration of docker-compose or optionally do automatically it through by modifying the root .env file.
Something like:

$ my_geonode docker (assuming django-admin has created a geonode-project called my_geonode)

docker-compose configuration
============================

GEONODE_HOST in .env file has to be as follow:

.env
----
GEONODE_HOST=localhost

$ my_geonode docker --config

GEONODE_HOST in .env file is being configured...
OK

After the manual/automatic configuration the stack can be launched as usual:

docker-compose up

[gannebamm]

I am not experienced in docker and django projects, but I would like to get an 'easy' way to create a docker based geonode-project for theming and other modifications. But I am not shure if we need a CLI for this, or 'just' good documentation. A CLI would make everything faster but for me would hide some of the underlying mechanisms which could lead to less understanding of the whole technique.

[francbartoli]

Thanks @gannebamm for your comment. The primary intent is to solve the question what's the address to use in order to configure properly the .env files for docker-compose up. Mostly of our users don't want to learn Docker and other stuff but just having a straightforward method to run the stack.

[olivierdalang]

-1 for CLI, which would be one more thing to maintain. Configuring the stack can be done simply by editing the .env (or setting env vars), which doesn't require much knowledge about Docker.

[francbartoli]

Hi @olivierdalang actually it does because you have certainly to know the ip address to use for .env or env vars. This proposal makes just life easier to know that information. Optionally it makes the editing for the user.

[giohappy]

what if we add this command to the paver tasks?

[francbartoli]

@giohappy it makes sense even though the idea was to add it to invoke tasks which would have an easier integration with setup.py