[PR #1115] [MERGED] Add gantry for automatically updating Docker services #1112

New Issue

GiteaMirror · 2025-11-06T12:14:58-06:00

GiteaMirror commented

2025-11-06 12:14:58 -06:00

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1115
Author: @shizunge
Created: 2/3/2024
Status: ✅ Merged
Merged: 2/3/2024
Merged by: @mashb1t

Base: master ← Head: master

📝 Commits (1)

beaa200 Add gantry for automatically updating Docker services

📊 Changes

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

View changed files

📝 README.md (+1 -0)

📄 Description

Quality Standards

Note that we can help you achieve those standards, just try your best and be brave.
We'll guide you to the best of our abilities.

To be on the list, it would be nice if entries adhere to these quality standards:

It should take less than 20 sec to find what is the project, how to install it and how to use it.
Generally useful to the community.
A project on GitHub with a well documented README.md file and plenty of examples is considered high quality.
Clearly stating if an entry is related to (Linux) containers and not to Docker. There is an awesome list for that.
Clearly stating "what is it" i.e. which category it belongs to.
Clearly stating "what is it for" i.e. mention a real problem it solves (even a small one). Make it clear for the next person.
If it is a WIP (work in progress, not safe for production), please mention it. (Remember the time before Docker 1.0 ? ;-) )
Always put the link to the GitHub project instead of the website!

To be on the list, the project must have:

How to setup/install the project
How to use the project (examples)

If your PR is not merged, we will tell you why so that you may be able to improve it.
But usually, we are pretty relaxed people, so just come and say hi, we'll figure something out together.

Rules for Pull Request

Each item should be limited to one link, no duplicates, no redirection (careful with http vs https!)
The link should be the name of the package or project or website
Description should be clear and concise (read it out loud to be sure)
Description should follow the link, on the same line
Entries are listed alphabetically, please respect the order
If you want to add more than one link, please don't do all PR on the exact same line, it usually results in conflicts and your PR cannot be automatically merged...

Please contribute links to packages/projects you have used or are familiar with. This will help ensure high-quality entries.

Your commit message will be a tweet so write a good commit message, keep that in mind :)

_{🔄 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/1115 **Author:** [@shizunge](https://github.com/shizunge) **Created:** 2/3/2024 **Status:** ✅ Merged **Merged:** 2/3/2024 **Merged by:** [@mashb1t](https://github.com/mashb1t) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`beaa200`](https://github.com/veggiemonk/awesome-docker/commit/beaa20087634042b6c399ae88ff6c87085b8ada1) Add gantry for automatically updating Docker services ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description    # Quality Standards Note that we can help you achieve those standards, just try your best and be brave. We'll guide you to the best of our abilities. To be on the list, it would be **nice** if entries adhere to these quality standards: - It should take less than 20 sec to find what is the project, how to install it and how to use it. - Generally useful to the community. - A project on GitHub with a well documented `README.md` file and plenty of examples is considered high quality. - Clearly stating if an entry is related to (Linux) containers and not to Docker. There is an [awesome list](https://github.com/Friz-zy/awesome-linux-containers) for that. - Clearly stating "what is it" i.e. which category it belongs to. - Clearly stating "what is it for" i.e. mention a real problem it solves (even a small one). Make it clear for the next person. - If it is a **WIP** (work in progress, not safe for production), please mention it. (Remember the time before Docker 1.0 ? ;-) ) - Always put the link to the GitHub project instead of the website! To be on the list, the project **must** have: - How to setup/install the project - How to use the project (examples) If your PR is not merged, we will tell you why so that you may be able to improve it. But usually, we are pretty relaxed people, so just come and say hi, we'll figure something out together. # Rules for Pull Request - Each item should be limited to one link, no duplicates, no redirection (careful with `http` vs `https`!) - The link should be the name of the package or project or website - Description should be clear and concise (read it out loud to be sure) - Description should follow the link, on the same line - Entries are listed alphabetically, please respect the order - If you want to add more than one link, please don't do all PR on the exact same line, it usually results in conflicts and your PR cannot be automatically merged... Please contribute links to packages/projects you have used or are familiar with. This will help ensure high-quality entries. #### Your commit message will be a [tweet](https://twitter.com/awesome_docker) so write a [good commit message](https://chris.beams.io/posts/git-commit/), keep that in mind :) --- <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 2025-11-06 12:14:58 -06:00

GiteaMirror closed this issue

2025-11-06 12:14:58 -06: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#1112