Odizy Workflow

Development

You can develop either locally on your own computer, or remotely in a Muppy-managed Development Server — see Code Server.

Create a branch for each new feature or bugfix, and open a merge request to use as the collaboration tool.

Test servers

Each time you commit on a feature branch, Muppy provisions or updates a Test Server, according to the parameters set in the App Definition, tab CICD LXC / Test Servers.

See Test Servers.

Staging servers

When you are satisfied with your development, you merge your changes — manually, or by closing the merge request. That commits them on the default branch.

Depending on the parameters in the App Definition, tab CICD LXC / Staging Servers, the Staging Server is then upgraded automatically or manually.

Staging servers run a copy of the production database, so this is where the upgrade is rehearsed on real data. See Restoring a Backup on a Staging Server.

Once your tests pass, tag the code — a tag gives you a release that is identified and easy to install.

Production servers

Deployment to production servers is manual.

For a High Availability production set, Muppy manages the deployment on every server of the set.