All Submissions you make to Magento Inc. (“Magento") through GitHub are subject to the following terms and conditions: (1) You grant Magento a perpetual, worldwide, non-exclusive, no charge, royalty free, irrevocable license under your applicable copyrights and patents to reproduce, prepare derivative works of, display, publically perform, sublicense and distribute any feedback, ideas, code, or other information (“Submission") you submit through GitHub. (2) Your Submission is an original work of authorship and you are the owner or are legally entitled to grant the license stated above. (3) You agree to the Contributor License Agreement found here: https://github.com/magento/magento2/blob/master/CONTRIBUTOR_LICENSE_AGREEMENT.html
Without Commerce Cloud license, Magento Community Edition users are not able to easily configure their local instances with Docker. The docker-compose.yml file can be generated using ece-docker which is not available for the open-source community.
The standalone docker-compose.yaml is not sufficient without the .docker directory that is created during compsoer update. Do you think it makes sense to attach it as is?
@shiftedreality What is the purpose of the .docker directory? docker-compose.yml is extremely useful for development purposes as we "refresh" the stack almost every day.
Preconditions
Without Commerce Cloud license, Magento Community Edition users are not able to easily configure their local instances with Docker. The
docker-compose.yml
file can be generated usingece-docker
which is not available for the open-source community.Proposed solution
docker-compose.yml
is added as an asset in https://github.com/magento/magento-cloud-docker/releasesExpected result
docker-compose.yml
is added as an asset in https://github.com/magento/magento-cloud-docker/releasesActual result
docker-compose.yml
for the open-source community.