# Running OpenELIS In Docker with Mounted locally Compiled Artifacts **URL:** \ **Category:** Development\ **Tags:** dev\_setup\ **Created:** [November 13, 2023, 7:31pm UTC](https://talk.openelis-global.org/t/running-openelis-in-docker-with-mounted-locally-compiled-artifacts/190 "2023-11-13T19:31:59Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Moses\_Mutesasira](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/moses_mutesasira/32/72_2.png) [@Moses\_Mutesasira](https://talk.openelis-global.org/u/Moses_Mutesasira)\ **Post date:** [November 13, 2023, 7:31pm UTC](https://talk.openelis-global.org/t/running-openelis-in-docker-with-mounted-locally-compiled-artifacts/190/1 "2023-11-13T19:31:59Z")
1. The Native way to [setup the dev](https://docs.openelis-global.org/en/latest/dev_setup/) environment requires Installing , configuring and Running the Tomcat server Locally. Some times that process becomes tedious for our new developers 2. The second option is [building](https://github.com/I-TECH-UW/OpenELIS-Global-2/tree/2.8#building-the-docker-images-directly-from-source-code) the docker images directly from source code. This Option is much easier ,given that one doesn’t need to setup and do all the ssl configurations for TomCat. But usually this option tends to be slower for testing changes given that you have to rebuild a new docker image on every change which tends to consume more time and resource 3. The Third Option. Doing the Builds(ie maven , npm) from the local dev enviroment, but mount the compiled artifacts into docker containers. This seems to be the easiest and fastest way to run OpenELIS from source code since it doesn’t require doing tedious tomcat configurations and also doesn’t require rebuilding the images on every change In Summary all the above are Options and anyone is free to choose a more easier Option based on the dev environment