Skip to content

OasisLMF/OasisUI

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8dbce21 · Feb 10, 2020
Feb 10, 2020
Sep 6, 2019
Jan 29, 2020
Feb 10, 2020
Jun 27, 2019
Feb 10, 2020
May 23, 2018
Feb 5, 2020
Mar 7, 2019
Mar 19, 2019
Jan 29, 2019

Repository files navigation

Oasis LMF logo

Build Status

Oasis UI

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

First Steps

Simple environment

TODO

Development

GitFlow

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.

Dependencies

TODO

Testing

TODO

Deploying

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

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

Documentation

License

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