[WIP] Update to use Docker 17.04 for improved performance

[andrerom]

Consists of three changes:

1. Use Docker 17.04 :cached (PR) volume mount point feature to improve performance
2. [WIP] Change nginx config to by default use SYMFONY_ENV=prod for backend & REST url's (/ez|/api)

Those two changes improves the performance to a level where working with containers is ok'ish, even on a older 2011 Macbook Pro.

Note: With changes we do in v2 and further improvements on docker itself last change for nginx conf might not be needed anymore (for people wanting to develop on backend they would anyway want it to also run in DEV)

Todo:

• JIRA Issue
• Link to blog post with performance numbers for this: https://ezplatform.com/Blog/A-look-at-Docker-for-Mac-17.04-Performance
• IF use of prod on backend is accepted:
  • Cleanup Nginx config
  • Adapt Apache config

Possible Followups:

• eZ Platform:
  • Optional: See if we can do something by default when running server:start as well to get backend to run in prod env (can probably be done with custom symfony server router, but unsure if we want to go back to that)
• Docker files:
  • Optional: Move docker compose and docker stuff a place where it can be used to generate flat docker-compose.yml file at root for simplified use (no need to always joggle which files to use)
  • Get rid of volume usage in prod so we can run on Docker Swarm
    • Affects anything that needs config, data or assets built in: solr, nginx, mariadb, varnish
  • Optional: See if we can move to alpine images now that it is supported by blackfire (but still not available for mysql/mariadb image)

---

How to run this:

Before you try, make sure you to install Docker 17.04 or higher (only available in Docker for Mac edge channel atm)!

For full instructions see the doc/docker-compose/Readme.md, short version for dev setup:

git clone --branch docker_17.04 https://github.com/ezsystems/ezplatform.git
cd ezplatform
export COMPOSE_FILE=doc/docker-compose/base-dev.yml
# If you have used this before make sure to run `docker-compose pull` first at this point!
docker-compose -f doc/docker-compose/install.yml up --abort-on-container-exit
docker-compose up -d --force-recreate

[timiTao]

any progress with this feature to add this to platform?

[andrerom]

@timiTao None, it was a prototype and would need cleanup on which folders use which mount options, and might need Docker for Mac to also gain support for :delegate

Also the need to run backend in prod disappears with v2 so cleanup should remove that as it's more of a hack. But the bump to docker compose 3.x format can be extracted and done on master right now if we want.

[DavidLiedle]

I have copied these edits into a private local repo and am running docker-compose successfully and without incident on my machine, as laid out in the README.md file, for a project I'm working on. Very nice! Thank you for these improvements @andrerom :) It has greatly sped up my development cycle.

EDIT: I happen to be on v1.10.0-rc3, as that's what was the latest when I started my current task. Forgot to mention the version earlier. :)

[timiTao]

@andrerom I run this on my local machine with ezPlatform + ee and working fine. I convince one person in Polish office to do that too on mac. Others consider this, with solution like that.

But we of them manually edit file base-dev.yml and ignore this changes in PR.

That is why I asked when will be this officialy 👍

Moving to new format always be some progress.

Funny things is that, it was one of first things in office to improve. After I did my job mostly, somebody told me from other office, that you did this PR - nobody used Docker For Mac in my office.

[andrerom]

Closing in favor of #192

NOTE: Concept for setting backend in PROD mode for v1 performance is not part of that, but can be opened separately for anyone that wants to try. Instead of the rewrite rules approach attempted here it should perhaps be:

• changes to web/index.php to set to prod when url matches /ez and /rest, and with a env variable to opt out of this
• changes to stash config to share cache between dev and prod when in file system mode

This way also php built in server (app/console server:start) can benefit to.