Setup automatic deployment #71

Open
opened 2021-05-12 12:14:09 +02:00 by Jef Roosens · 0 comments
Owner
  • Release deployment

Whenever a tag is pushed to the master branch, I'd like the following things to happen:

  • Build a new Docker image & push it to a registry
  • Deploy this new image on the fej.roosens.me server.
  • Develop deployment

The same should happen when pushing to develop, but this should create the dev tag instead of the actual version tag. Furthermore, I'd like to constantly deploy the develop branch on https://fej.roosens.me/next, allowing my development to be followed by my friends if they so choose. Before we can do this, we need to implement #22.

  • Docs & frontend

This should just happen automatically, because the static files will be embedded one way or another.

- [ ] Release deployment Whenever a tag is pushed to the master branch, I'd like the following things to happen: * Build a new Docker image & push it to a registry * Deploy this new image on the [`fej.roosens.me`](https://fej.roosens.me) server. - [ ] Develop deployment The same should happen when pushing to `develop`, but this should create the `dev` tag instead of the actual version tag. Furthermore, I'd like to constantly deploy the `develop` branch on `https://fej.roosens.me/next`, allowing my development to be followed by my friends if they so choose. Before we can do this, we need to implement #22. - [ ] Docs & frontend This should just happen automatically, because the static files will be embedded one way or another.
Commenting is not possible because the repository is archived.
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Chewing_Bever/fej#71
No description provided.