[PR #1521] [MERGED] Add Granite Registry to the Registry section #38140

Closed
opened 2026-08-20 02:56:00 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1521
Author: @mazanax
Created: 8/4/2026
Status: ✅ Merged
Merged: 8/18/2026
Merged by: @veggiemonk

Base: master ← Head: add-granite-registry


📝 Commits (2)

  • a4bebdb Add Granite Registry to the Registry section
  • ceb7dc0 Merge branch 'master' into add-granite-registry

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Adds a managed private Docker registry to ### Registry.

- [Granite Registry](https://granite.so/products/docker-registry) - :yen: Store private Docker images alongside the workloads that pull them, with scoped read-only and read-write keys.

The "for Docker" test

I want to be upfront, because the honest answer is different depending on what is being submitted.

Granite as a whole is an application platform, and it fails your test — take Docker away and it is still a Git-deploy PaaS. So I am not submitting the platform, and not proposing an entry in Deployment & Platforms.

What I am submitting is its registry. "This project exists to store and serve private Docker images." Remove Docker and there is nothing left, and your guidelines name registry in the accept list directly. Its peers in this section — ECR, Azure Container Registry, Cloudsmith, GCP Artifact Registry, JFrog — are the same shape: commercial managed registries linking to a product page.

Entry rules

  • One link per entry.
  • :yen: set, it is a paid service (from $9/month, no free tier).
  • Inserted alphabetically between GitLab Container Registry and Harbor, case-insensitive.
  • One sentence, leads with the verb, and the Docker connection is in the description rather than implied.
  • Links to the product page rather than a repository — the service is not open source, so there is no repo to point at. Same as the other commercial entries in this section.
  • Active: in open beta since October 2025, shipping monthly.

What it does

Plain Docker protocol, no special client — docker login, docker push, docker pull and any existing CI job work unchanged. Private by default: nothing is listed or published, and every pull and push needs a key you issued. Keys come in read-only and read-write-delete, revocable one at a time. No cap on repositories or images. Images are pulled from inside the platform that runs them, and pushing a tag can trigger a redeploy.

Disclosure

I work on Granite, so this is a self-submission. Flagging it rather than leaving you to notice.

This PR was assisted by AI (Claude): finding the right section, checking the entry rules against the guidelines and drafting this description. The claims above are mine and are all verifiable on the linked page.

make lint passes locally.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1521 **Author:** [@mazanax](https://github.com/mazanax) **Created:** 8/4/2026 **Status:** ✅ Merged **Merged:** 8/18/2026 **Merged by:** [@veggiemonk](https://github.com/veggiemonk) **Base:** `master` ← **Head:** `add-granite-registry` --- ### 📝 Commits (2) - [`a4bebdb`](https://github.com/veggiemonk/awesome-docker/commit/a4bebdb850e545a521629951167e035e71695906) Add Granite Registry to the Registry section - [`ceb7dc0`](https://github.com/veggiemonk/awesome-docker/commit/ceb7dc0401c6b42a31d07d9e41c0587da45d6677) Merge branch 'master' into add-granite-registry ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Adds a managed private Docker registry to `### Registry`. ``` - [Granite Registry](https://granite.so/products/docker-registry) - :yen: Store private Docker images alongside the workloads that pull them, with scoped read-only and read-write keys. ``` ### The "for Docker" test I want to be upfront, because the honest answer is different depending on what is being submitted. Granite as a whole is an application platform, and it **fails** your test — take Docker away and it is still a Git-deploy PaaS. So I am not submitting the platform, and not proposing an entry in `Deployment & Platforms`. What I am submitting is its registry. *"This project exists to store and serve private Docker images."* Remove Docker and there is nothing left, and your guidelines name `registry` in the accept list directly. Its peers in this section — ECR, Azure Container Registry, Cloudsmith, GCP Artifact Registry, JFrog — are the same shape: commercial managed registries linking to a product page. ### Entry rules - One link per entry. - `:yen:` set, it is a paid service (from $9/month, no free tier). - Inserted alphabetically between GitLab Container Registry and Harbor, case-insensitive. - One sentence, leads with the verb, and the Docker connection is in the description rather than implied. - Links to the product page rather than a repository — the service is not open source, so there is no repo to point at. Same as the other commercial entries in this section. - Active: in open beta since October 2025, shipping monthly. ### What it does Plain Docker protocol, no special client — `docker login`, `docker push`, `docker pull` and any existing CI job work unchanged. Private by default: nothing is listed or published, and every pull and push needs a key you issued. Keys come in read-only and read-write-delete, revocable one at a time. No cap on repositories or images. Images are pulled from inside the platform that runs them, and pushing a tag can trigger a redeploy. ### Disclosure I work on Granite, so this is a self-submission. Flagging it rather than leaving you to notice. This PR was assisted by AI (Claude): finding the right section, checking the entry rules against the guidelines and drafting this description. The claims above are mine and are all verifiable on the linked page. `make lint` passes locally. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-08-20 02:56:00 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#38140