Release v1.0.0: Docker volumes (breaking changes)

[cytopia]

Docker volumes

READFIRST

This branch is constantly being rebased from master until final merge, therefore requires git force pushing. Keep this in mind when checking it out via git.

Feedback

To move on faster and pain-free, please try out this branch and provide your Feedback. I will update the description correspondingly.

• Tested on Linux
• Tested on Windows (native)
• Tested on MacOS (native)
• Tested on Windows (Docker Toolbox)
• Tested on MacOS (Docker Toolbox)

Also ensure the following has been done:

• Ensure that named volumes have their own configuration for mount options (similar to MOUNT_OPTIONS)

Notes on this PR

This PR will be merged into release/v1.0.0

DESCRIPTION

This PR will move all data directories (MySQL, PostgreSQL, MongoDB and others) to Docker volumes for best-practice and compatibility reasons on different operating systems.

This is mainly a huge step for Windows user as they seem to have issues with current Docker mounts over and over again. However it should also generally increase performance for all other systems.

IMPORTANT

When using this branch, you will loose all you current data for MySQL, PostgreSQL and MongoDB, so ensure to make a backup first.

• Backup Mysql
• Backup PostgreSQL
• Backup MongoDB

Once you have backed up everything, start the Devilbox from this branch and import your data.

Fixes

• Refs: Using Docker for Windows to volume-mount a Windows drive into a Linux container is bad #175
• Refs: MySQL doesn't start on Windows with Docker Toolbox #382

Usage

Stop the Devilbox

docker-compose stop
docker-compose rm

Update Git and change to the new branch

git fetch --all --prune
git checkout docker-volumes
git pull origin docker-volumes

Compare env-example with .env for changes

Start the Devilbox

docker-compose up

[fkaminski]

I can confirm this - branch tested with:

• Tested on Windows ( Docker Toolbox with version v18.09.0 )

Question: But why we need the use of Docker Volumes here at all?

Before i test devilbox i am using this repo for my favorite CMS contao.org:
https://github.com/ctsmedia/docker-contao/blob/master/docker-compose.yml

The "db" service uses just the mysql image.
For Import/Export one could use phpmyadmin or "docker exec" with mysqldump or mysql commands ...

[cytopia]

Awesome, thanks @fkaminski!

This branch is currently a bit behind due to many fixes on master. I will update this during the weekend.

Note: I will rebase master into this one (to keep history more clean), this is going to be a force push.

[mrpsiho]

Confirm that:

• Tested on MacOS (native) (Docker 2.0.0.2)

It works for me.

[cytopia]

@mrpsiho Thanks for the feedback!

[cytopia]

@fkaminski @mrpsiho I've rebased latest master into this branch and force-pushed the changes.

[fkaminski]

I've rebased latest master into this branch and force-pushed the changes.

Thanks, now i cannot call phpmyadmin - seems like the #342 issue.
When i change ".devilbox/www/htdocs/vendor/phpmyadmin-4.8/config.inc.php" to readonly again -
then it works ...

[fkaminski]

Beside that -
the autodns feature do work here also with docker toolbox and Virtualbox port forwarding mentioned in
#411 (comment)

[cytopia]

Thanks, now i cannot call phpmyadmin - seems like the #342 issue.
When i change ".devilbox/www/htdocs/vendor/phpmyadmin-4.8/config.inc.php" to readonly again -
then it works ...

@fkaminski thanks for the info. I am fixing it and also adding a CI check to ensure this error will never get back into the git repository: #488

FYI: I cannot add file permissions to git except for executable or not executable, so I will have to add $cfg['CheckConfigurationPermissions'] = false; to make sure it works everywhere.

[cytopia]

Work on Docker Volumes will be prioritized and to ensure backwards compatibility with current users tagged separately on the Release branch, hence v0.x and v1.x will co-exist simultaneously until everything has been furnished.

[cytopia]

Use the following branch (which wil also receive tagging): #416