Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Taken from oms-docker github:




To do anything, just know you have to be in the host VM (accessible through `vagrant ssh` ).
Once logged in, `cd ~/oms-docker/docker` to run all the `docker-compose` commands

To stop everything, run `docker-compose down` in the folder. You can start everything again with `docker-compose up -d` Other than that, you should have a working dev-environment by now. If something breaks during development, you can try rebuilding everything with `docker-compose build`. Maybe also calling the bootstrap scripts again could help, but in theory they should only be needed upon creation.

With `docker ps` you can see which containers are currently running. If you want to "log into" the omscore, you can run `docker-compose exec omscore bash`. For omsevents run `docker-compose exec omsevents bash`

# Credits
This repo was loosely based upon laradock, the docker-alternative to the native homestead.

  • No labels