Commit d53ddb3f authored by Buskermolen, Joost's avatar Buskermolen, Joost
Browse files

Added explanation

parent 06262ed8
# leuven.isric.org
| Name | URL | Branch |
|-------------|----------------------------------------|--------|
| Development | https://leuven.containers.wur.nl | Master |
| Production | https://leuven.isric.org | Develop |
## How it works
This application will be automatically deployed to the development environment when a commit within the `develop` branch has a commit message that starts with either:
* fix: \<COMMIT MESSAGE>
* feat: \<COMMIT MESSAGE>
For example:
`git commit -m 'fix: Typo in maps.html'`
Or:
`git commit -m 'feat: Added new page contact.html'`
## Details
When using the prefixes as shown above in front of your commit message, a process is automatically started. This process will automate the following:
1. Tag your commit with a subsequent version number [PROD ONLY]
2. Build and tag a container with this version number [DEV gets a unique SHA]
3. Push the container to [our centralised repository](https://harbor.containers.wurnet.nl)
4. Modify `kustomization.yaml` manifest in [k8s-deployments repository](https://git.wur.nl/isric/ict/k8s-deployments/-/tree/master/leuven/overlays/dev) to deploy the new container to the [Development environment](https://leuven.containers.wur.nl)
## From Development to Production
If you're happy with the Development version and want to deploy it to Production, just merge your changes to master.
>The version that's currently running on Development will now be automatically deployed to Production
---
Intro
-----
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment