1

We're serving Python packages through Google's Artifact Registry. Actually the URL is the "default" one, so

https://[REGION].pkg.dev/[PROJECT_ID]/.....

but what if we wanted to use a custom domain name? For example we'd like to serve packages from a custom domain link like

https://[MY-CUSTOM-DOMAIN]/...

Is there an official way to do that? What are my options?

Wytrzymały Wiktor
  • 11,492
  • 5
  • 29
  • 37
paoloyx
  • 575
  • 1
  • 7
  • 12
  • Does this [article](https://cloud.google.com/blog/topics/developers-practitioners/hack-your-own-custom-domains-container-registry) answer your question? "...you can simply use your existing Google Container Registry or Artifact Registry to store your images, and build a "reverse proxy" on top of it to forward the incoming requests while still serving the traffic on the custom domain name you own." – Farid Shumbar Jan 18 '22 at 16:12
  • 1
    @FaridShumbar yes, that's actually what a Google Community Team member told me, see [this post](https://www.googlecloudcommunity.com/gc/Infrastructure-Compute-Storage/Custom-domain-name-to-serve-Python-packages-from-Google-Artifact/m-p/184239#M437). Thank you, seems that the reverse proxy is the only way to go – paoloyx Jan 20 '22 at 09:11

1 Answers1

1

Posting my comment for visibility.

Consider using the reverse proxy as described in the article:

...you can simply use your existing Google Container Registry or Artifact Registry to store your images, and build a "reverse proxy" on top of it to forward the incoming requests while still serving the traffic on the custom domain name you own.

Farid Shumbar
  • 1,360
  • 3
  • 10