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.

Sign up for GitHub

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

Jump to bottom

Docker Compose instead of starting separately #110

Open
sdonovan1985 opened this issue May 4, 2019 · 2 comments
Open

Docker Compose instead of starting separately #110

sdonovan1985 opened this issue May 4, 2019 · 2 comments

Comments

@sdonovan1985
Copy link
Collaborator

Starting separately is useful, especially for testing, but for deployment, docker compose is easier and much cleaner.
sdonovan1985 pushed a commit that referenced this issue Sep 24, 2019
#110 - First pass at an example docker-compose.yml. Need to test in VM.
cdbbac4
sdonovan1985 pushed a commit that referenced this issue Sep 24, 2019
#110 - Ok, made changes and this is working on my local test VM.
c4bdfc6
sdonovan1985 pushed a commit that referenced this issue Sep 24, 2019
#110 - docker-compose.yml for SoX.
1ec4e9b
@sdonovan1985
Copy link
Collaborator Author

The SoX docker-compose.yml hasn't been tested - it's in the cleanup branch, not in the master branch.

Next question: should I use docker-compose for Miami? I'd get free auto-restart from it.

@sdonovan1985
Copy link
Collaborator Author

OK, to get this to work with Jenkins, the Jenkins build steps need to change. Right now, they're calling the start scripts. The build would require docker-compose to be installed at the beginning, then running docker-compose rather than calling a bash script.

@sdonovan1985 sdonovan1985 mentioned this issue Dec 4, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdonovan1985