Insert Mysql Docker container code and instructions

[anselmix80]

Can we implement dotenv library and create .env file with all variables? This will be useful to have all variables in a single place, outside the .py files...
Another thing is to use 'HOST': '127.0.0.1', instead of 'HOST': 'localhost'. With this change we can create container of mysql and we don't need to install mysql engine on of workstation.

[DjangoCRM]

I think we should try not to complicate the project. Especially for those who do not need to use Docker or for less experienced users.

[anselmix80]

Dot Env is separate topic, we can use dot env to list all variables in a file outside the code. From my point of view it means we are going to semplify the use experience of the application

[DjangoCRM]

As I understood from #128, to support Docker it is enough to change localhost to 127.0.0.1 in the DATABASES settings in the settings.py file. Yes, using localhost is a little bit faster, but to support Docker while maintaining the simplicity of the CRM project, I think we can do it.

[anselmix80]

Thank you for that, I will make a new pull for MySql and Docker.
For DotEnv implementation, do you think to merge it? Do you want that I update readme file?

[DjangoCRM]

As I see in #133, after DotEnv implementation, we can no longer claim that Django-CRM installs like a normal Django project. But we have to stick to it.
I think a compromise might be to create a separate repo for Docker support, as is done in many projects.
It is better to add installation instructions to the docs/installation_and_configuration_guide.md file.

[anselmix80]

So you mean to split DotEnv and Docker. This is clear.
But can we implement the use of DotEnv in your main repository and docker in a separate repo?

[DjangoCRM]

No. What I meant was that we could add the Docker file to the master branch if it was enough to change the localhost in the settings file to 127.0.0.1.
If this is not possible and the DotEnv should be used, then the support of the Docker in a separate repo (of course on the project account) or branch.
Anyway, as we already discussed, i can merge something regarding Docker only after getting community review.

[anselmix80]

The only change necessary to manage the Docker MySQL image is to set HOST = 127.0.0.1 in webcrm/settings.py.

I have the pull request, re-added docker folder with dedicated files and reorganized the installation_and_configuration_guide.

Can we discuss the implementation with the community?

DotEnv is another topic that we can discuss in a dedicated thread.

[DjangoCRM]

Thank you for your efforts.
You wrote a good text about MySQL Container (#140) but it is redundant for the main installation and configuration instructions.
Maybe such text would be good for a file in the docker folder.
But in any case it should not look like an advertisement for Docker.
The main instructions may include a short mention of MySQL Container after the rest of the files have received positive community review and are merged into the project.
Regarding the docker folder.
What if other users want to add a container for PostgreSQL?

[anselmix80]

To implement PostgreSQL, a user must:

1. Create a docker compose or a docker command to download PostgresSQL image istead of MySQL image
2. Change settings.py to use driver and port of PostgreSQL
   Not mandatory, create a new .sh to run that compose file or docker command to run all

[DjangoCRM]

So, will it be necessary to change existing files?
That's why I'm asking.
Maybe then the containers for these databases should be placed in separate subdirectories?

[anselmix80]

If the comunity will accept the implementation of container for MySQL, I will implement this:
"Maybe such text would be good for a file in the docker folder." and fix main installation file

[DjangoCRM]

Ok
But for now, please remove the main installation file from PR #140

[anselmix80]

Ok done, created dedicated how to use file under docker folder