Web-based application client for managing exposure data and operating modelling workflows.There are three components:

• Shiny UI application
• Python Flask server providing services for interacting with exposure and output data
• SQL server database

TODO

We use the GitFlow model described here .

The main idea is that the central repo holds two main branches with an infinite lifetime:

• master: main branch where the source code of HEAD always reflects a production-ready state
• develop: main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release. This is where our automatic builds are built from.

When the source code in the develop branch reaches a stable point and is ready to be released, all of the changes should be merged back into master. Feature branchs should be used for new features and fixes, then a Pull Request isues to merge into develop.

TODO

TODO

The Oasis CI system builds and deploys the following Docker images to DockerHub:

• coreoasis/flamingo_server
• coreoasis/shiny_proxy

Note that the Dockerfiles cannot be used directly as there are version stubs that get substitued at build time by the CI system.

TODO DB setup

• Issues
• Releases
• General Oasis documentation
• Using the Oasis UI

The code in this project is licensed under BSD 3-clause license.