GitHub Package Registry VS Google Container Registry

GitHub Package Registry is a package hosting service provided by GitHub. It allows you to publish, share, and manage software packages directly within your GitHub repositories. - Source: dev.to / 5 months ago

Ideally you run your the build step on CI and push the built image into container registry (like dockerhub or ghcr). You can then download the image on server and run it. You can do this with docker-compose as well, just use the image instead of dockerfile to define your web app like you do with proxy and DB. Source: about 1 year ago

Package Hosting & Container Registry (Free for public repos,500 MB storage & 1GB bandwidth outside CI/CD free for private repos). - Source: dev.to / over 1 year ago

There are more Container registries but Docker Hub, such as Github Registry, Amazon ECR, to name a few. We can change the registry anytime by using the command docker login. - Source: dev.to / over 1 year ago

You can use your github account as your own NPM registry using github packages. Source: almost 2 years ago

Artifact Registry: artifact storage to manage container images. - Source: dev.to / 4 months ago

How push those images into a registry (preferably GCR)? Source: about 1 year ago

If you wish to use Google Container Registry, you can run the following. - Source: dev.to / over 1 year ago

Pretty much language agnostic given that it’s just running docker images you build and deploy to GCP Container Registry. Source: over 1 year ago

In this article we will learn how to connect GCP's code versioning service (Cloud Source Repositories) to Cloud Build to automate building Docker images and pushing them to GCP Container Registry. - Source: dev.to / over 1 year ago