Skip to content
New issue

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

Replace calls to docker composer by API calls #9

Closed
gdethier opened this issue Jul 19, 2017 · 2 comments
Closed

Replace calls to docker composer by API calls #9

gdethier opened this issue Jul 19, 2017 · 2 comments
Assignees
Milestone

Comments

@gdethier
Copy link
Owner

gdethier commented Jul 19, 2017

Currently, docker composer is called via an explicit process execution. Docker composer should be replaced by calls to Docker API. Indeed, the user of composer is simple enough to be replaced by a manual setup via the API.

@gdethier gdethier changed the title Replace calls to docker client by API calls Replace calls to docker composer by API calls Apr 10, 2018
@gdethier gdethier added this to the 0.2 milestone Apr 10, 2018
@gdethier gdethier self-assigned this Apr 10, 2018
gdethier added a commit that referenced this issue Apr 11, 2018
gdethier added a commit that referenced this issue Aug 13, 2018
@gdethier
Copy link
Owner Author

Before closing this issue, data volumes management should be addressed (allow them to remain upon clear action but add option to delete them later and/or at the same time).

@gdethier
Copy link
Owner Author

A volume has been added to keep WP files in addition to DB data. Volumes are not cleared automatically so a start/clear/start sequence does not loose data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant