The LMS and Studio (CMS) are now part of devstack!

ECOM-6560

ECOM-6560

- Pulling custom Elasticsearch image from Docker Hub
- Using data volumes instead of host directories for Elasticsearch and MySQL data. (This should help mitigate file system slowness on OS X.)

ECOM-6560

ECOM-6570

ECOM-6560

- Waiting for MySQL container to come online before provisioning databases
- Creating superusers for each service
- Populating countries for the E-Commerce Service
- Using devstack URLs for the Catalog/Discovery Service partner
- Compiling static assets for each service (except programs, which has no static assets)

ECOM-6560

This adds a script for creating a loopback alias and adding a corresponding entry to /etc/hosts on OS X machines. See the README additions for more details. The script can be run with a Make target, which in turn is run by `devstack.start` to avoid any manual steps.

ECOM-6586

This alleviates issues that occur when the DB-dependent services start before the MySQL container has time to run the entrypoint script.

ECOM-6563

This is temporary until the configuration is merged. See https://github.com/edx/configuration/pull/3098.

ECOM-6561

ECOM-6565

Also ties in the clone script: repos are cloned if they don't exist when starting and opening devstack.

ECOM-6583

This custom image includes the elasticsearch-head plugin

Fixes #8

The docker-compose file is now validated with very push.

ECOM-6561

Use requirements ranges to avoid having to update the requirements file too frequently. Also adds a Make target for installing requirements.

The included script is idempotent, executed when the mysql container is initialized. This approach is borrowed from https://github.com/docker-library/mysql/pull/18.

ECOM-6563

ECOM-6561

This file brings all of the third-party and edX services online. Additionally, a directory has been created for shared volumes. A Makefile is included to simplify the starting and stopping of the services.

ECOM-6561

ECOM-6560

Python 3 script for cloning Git repos housing edX services. These repos are mounted as data volumes into their corresponding Docker containers to facilitate development. Repo clone URLs can be found in settings.yml. Repos are cloned to the directory above the one housing this file.

ECOM-6562