GitHub Actions Update

[gittrekt]

Updated action CI/CD

• Added building for amd64/arm64
• Added build on tag version push
• Fixed depreciated actions usage
• Added docker build-cache for build speed improvement (maybe we could move this to a seperate docker repo?)

[gittrekt]

A few points to mention:

1. When a new tag is pushed it must be in the format v0.0.0 (same as we currently do.) The docker release will be named as that tag, and latest
2. Running workflow dispatch will release as the same name as branch (ex: main or develop)
3. A buildcache image is also generated and uploaded. Future builds that don't have fundamental system changes will build much faster. (Note that alpine apk updates may cause a forced full rebuild.) The buildcache could be placed under it's own repo and any other future things we build with github actions in docker could also be placed under that repo with a different tag.

[ohager]

lgtm - maybe at least some docs update for deployment, would be nice

[ohager]

When I created the workflow, I was a bit hesitant to use a required tag format, as it was not 100% established flow.. And I'm still a bit hesitant...although, I consider this as good practice. jfyi - We should

1. describe the exact deployment flow in the docs
2. Maybe introduce a bash/batch script release.sh --minor or something for consistent runs

[gittrekt]

The version tags work very well at this point. I think it should be good for this use case.

The runs should be consistent other than workflow_dispatch. I can take a second look and maybe see if we can use consistent naming in workflow_dispatch case to also use version tags. I have a few private repos that use them without problems, assuming the right release tags are used (v0.0.0 or v0.0.0-RC1).

I can throw comments in. I'm always bad at documentation 😆

[gittrekt]

I had to rename my branch due to a conflict. Will have to open new PR. @ohager