[PR #636] [MERGED] Add Bash utils for Portainer stacks #724

New Issue

GiteaMirror · 2025-11-06T12:05:30-06:00

GiteaMirror commented

2025-11-06 12:05:30 -06:00

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/636
Author: @greenled
Created: 11/25/2018
Status: ✅ Merged
Merged: 11/26/2018
Merged by: @veggiemonk

Base: master ← Head: patch-1

📝 Commits (2)

e47414c Add Bash utils for Portainer stacks
16236df Update Portainer stack utils description

📊 Changes

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

View changed files

📝 README.md (+1 -0)

📄 Description

https://github.com/greenled/portainer-stack-utils

A Bash script to deploy/update/undeploy Portainer stacks. Portainer already provides a great web user interface to manage Docker instances and a REST API, but no official command line client. This script wraps some Portainer API endpoints related with stacks deployment, allowing an easier and less error prone continuous deployment setting. Conveniently, a Docker image of the script is also provided, so it can be used right away as part of a CI/CD pipeline.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines
The project submitted conforms to the quality standards outlined in the contribution guidelines
Go to the contribution guidelines and read it again.

RULES (because you probably didn't read the guidelines):

Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.

FORMAT
- Use the following format: [Name](Link) - Description.
- [Name] should be the title of the project
- (Link) should be pointing to a GitHub repository, not to a website
- Description. should end with a full stop/period
- For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)
ORDER: The entries are in lexical order (English letter order)
LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.
- 💲 indicates if one needs a paying subscription to use the project.
- 🚧 indicates that the project is a work in progress/beta release.
- 💀 indicates that the project is obsolete, but still worth mentioning it.

_{🔄 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/636 **Author:** [@greenled](https://github.com/greenled) **Created:** 11/25/2018 **Status:** ✅ Merged **Merged:** 11/26/2018 **Merged by:** [@veggiemonk](https://github.com/veggiemonk) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`e47414c`](https://github.com/veggiemonk/awesome-docker/commit/e47414ca69ca8110638e980402dd2b022896ba6a) Add Bash utils for Portainer stacks - [`16236df`](https://github.com/veggiemonk/awesome-docker/commit/16236df91b26f0a5e1af09c18daf8497581151f6) Update Portainer stack utils description ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description   https://github.com/greenled/portainer-stack-utils A Bash script to deploy/update/undeploy Portainer stacks. Portainer already provides a great web user interface to manage Docker instances and a REST API, but no official command line client. This script wraps **some** Portainer API endpoints related with stacks deployment, allowing an easier and less error prone continuous deployment setting. Conveniently, a Docker image of the script is also provided, so it can be used right away as part of a CI/CD pipeline. # By submitting this pull request I confirm I've read and complied with the below requirements. **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** - I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) - The project submitted conforms to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) - Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) and read it again. **RULES (because you probably didn't read the guidelines):** Links will be tested with [awesome_bot](https://github.com/dkhamsing/awesome_bot). Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of `README.md` file. - FORMAT - Use the following format: `[Name](Link) - Description.` - `[Name]` should be the title of the project - `(Link)` should be pointing to a GitHub repository, not to a website - `Description.` should end with a full stop/period - For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like `By [@author](GitHub account)` - ORDER: The entries are in lexical order (English letter order) - LABEL (Optional): Add one of the following icons next to the project name like ```[Name](Link) :icon: - Description.``` - :heavy_dollar_sign: indicates if one needs a paying subscription to use the project. - :construction: indicates that the project is a work in progress/beta release. - :skull: indicates that the project is obsolete, but still worth mentioning it. --- <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:05:30 -06:00

GiteaMirror closed this issue

2025-11-06 12:05:31 -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#724