CI workflow to push docker image to github packages

[bitner]

Push releases to GitHub packages docker registry.

Fixes #19

[lossyrob]

@bitner looking to get a 0.2.8 release out as the ingestion is broken in 0.2.7 and it's blocking testing of pgstac on stac-fastapi; I'm fine manually tweaking version numbers and will have a PR up to review in a bit that should be good for the release; is there any reason not to merge this to also have a 0.2.8 image to work with from gcr?

[lossyrob]

it's blocking testing of pgstac on stac-fastapi

This may not be true, looks like the testing env is generally botched on my machine; but generally would be good to get a release with 26df853 out

[vincentsarago]

@bitner any reason not to push to dockerhub and GitHub?

ref: https://github.com/developmentseed/titiler/blob/master/.github/workflows/ci.yml#L142-L152

[bitner]

@bitner any reason not to push to dockerhub and GitHub?

ref: https://github.com/developmentseed/titiler/blob/master/.github/workflows/ci.yml#L142-L152

@vincentsarago my immediate response is lazily that ghcr.io doesn't require me to find any additional credentials

[bitner]

Closing this PR, I wrapped this into #24

[lossyrob]

@vincentsarago also Dockerhub has user account restrictions # for free organization (e.g. stac-utils on dockerhub), and doesn't allow you to publish with org-specific credentials. We got in a situation where we thought we may have to publish to stac-utils dockerhub with a developers account creds, I went to make a bot account instead, but we were already at the limit for the org...then we found out GCR would solve all of these problems and have been focusing on that as a docker publishing platform since.