What's Up, Dock(er)? A slightly more visual way to interact with the docker daemon. Supdock is a wrapper for the docker command meaning you can still use all of the other docker commands without issues.
Most of the user interface enhancing community projects for Docker take Docker that slight bit too far. Supdock aims at optimising your workflow without bringing too much overwhelming changes to your standard docker usage.
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.
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/517
**Author:** [@segersniels](https://github.com/segersniels)
**Created:** 2/9/2018
**Status:** ✅ Merged
**Merged:** 2/10/2018
**Merged by:** [@veggiemonk](https://github.com/veggiemonk)
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (2)
- [`e69feff`](https://github.com/veggiemonk/awesome-docker/commit/e69feff1a843a0536d47807814b351c84438d42b) added supdock to UI terminal section
- [`1511aaa`](https://github.com/veggiemonk/awesome-docker/commit/1511aaaf63c3a739258e49323569e319c205d9af) Update README.md
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
What's Up, Dock(er)? A slightly more visual way to interact with the docker daemon. Supdock is a wrapper for the docker command meaning you can still use all of the other docker commands without issues.
<!-- Congrats on creating an Awesome Docker entry! 🎉 -->
<!-- Please fill in the below placeholders -->
https://github.com/segersniels/supdock
Most of the user interface enhancing community projects for Docker take Docker that slight bit too far. Supdock aims at optimising your workflow without bringing too much overwhelming changes to your standard docker usage.
# 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/CONTRIBUTING.md)
- The project submitted conforms to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/517
Author: @segersniels
Created: 2/9/2018
Status: ✅ Merged
Merged: 2/10/2018
Merged by: @veggiemonk
Base:
master← Head:patch-1📝 Commits (2)
e69feffadded supdock to UI terminal section1511aaaUpdate README.md📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
What's Up, Dock(er)? A slightly more visual way to interact with the docker daemon. Supdock is a wrapper for the docker command meaning you can still use all of the other docker commands without issues.
https://github.com/segersniels/supdock
Most of the user interface enhancing community projects for Docker take Docker that slight bit too far. Supdock aims at optimising your workflow without bringing too much overwhelming changes to your standard docker usage.
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.mdfile.[Name](Link) - Description.[Name]should be the title of the project(Link)should be pointing to a GitHub repository, not to a websiteDescription.should end with a full stop/periodBy [@author](GitHub account)[Name](Link) :icon: - Description.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.