We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It may be better to follow a more modular approach for architecture. For example:
. ├── bin ├── docker-compose.yml ├── lib │ └── services │ ├── httpd │ │ ├── docker-compose.httpd.yml │ │ └── etc │ │ └── httpd.conf │ ├── mysql │ │ ├── docker-compose.mysql.yml │ │ ├── etc │ │ │ └── mysql.conf │ │ └── lib │ │ └── data │ ├── node │ │ ├── docker-compose.node.yml │ │ └── lib │ │ └── npm-packages │ └── php │ ├── docker-compose.php.yml │ ├── etc │ │ └── php.ini │ └── lib ├── Makefile ├── README.md └── tmp
# docker-compose.yml version: "2" services: httpd: extends: file: 'services/httpd/docker-compose.httpd.yml' service: httpd
This will make it easier for scaffolding and will just generally be tidier.
The text was updated successfully, but these errors were encountered:
Added in a2d8b14
Sorry, something went wrong.
No branches or pull requests
It may be better to follow a more modular approach for architecture. For example:
This will make it easier for scaffolding and will just generally be tidier.
The text was updated successfully, but these errors were encountered: