DepCharge alternatives and similar packages
Based on the "DevOps Tools" category.
Alternatively, view DepCharge alternatives based on common mentions on social networks and blogs.
-
Moby
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems -
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD -
Packer
Packer is a tool for creating identical machine images for multiple platforms from a single source configuration. -
kubeshark
The API traffic analyzer for Kubernetes providing real-time K8s protocol-level visibility, capturing and monitoring all traffic and payloads going in, out and across containers, pods, nodes and clusters. Inspired by Wireshark, purposely built for Kubernetes -
Ddosify
Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud -
Mizu
DISCONTINUED. The API traffic viewer for Kubernetes providing deep visibility into all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster. Think TCPDump and Wireshark re-invented for Kubernetes [Moved to: https://github.com/kubeshark/kubeshark] -
dasel
Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package. -
Pomerium
Pomerium is an identity and context-aware reverse proxy for zero-trust access to web applications and services. -
Fleet device management
Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center) -
StatusOK
Monitor your Website and APIs from your Computer. Get Notified through Slack, E-mail when your server is down or response time is more than expected. -
s3gof3r
Fast, concurrent, streaming access to Amazon S3, including gof3r, a CLI. http://godoc.org/github.com/rlmcpherson/s3gof3r -
uTask
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
InfluxDB - Power Real-Time Data Analytics at Scale
Do you think we are missing an alternative of DepCharge or a related project?
Popular Comparisons
README
DepCharge
DepCharge is a tool that helps orchestrate the execution of commands across the many dependencies and directories in larger projects. It also provides an excellent mechanism for self-documenting a project's vast (and often disparate) dependencies.
Sneak peek:
depcharge --labels=api -- git clone {{repo}} {{location}}
Will run git clone
across all listed git dependencies with the label of "api" in your project (where submodules use to rule the land)
Introduction
By creating a YAML file that describes all of your project(s) dependencies, you can then execute commands across all of them simultaneously.
A medium-to-large sized project (especially when using a microservice architecture) will consist of 3 or more separate repositories, and rely on a variety of package managers depending on the various languages chosen for each service. Typically, these repos must be managed, tracked, and released in some semblance of unison so that the dependant service calls can be understood and responded to appropriately.
For small (to single) teams, a single developer will often need to propagating and perform the same commands across all relevant services. This is a tedious, manual, and error-prone process that can occur every release.
DepCharge is designed to help fix that.
How it Works & Usage
DepCharge is a tool designed to help orchestrate the execution of commands across many directories at once. All of the examples here are just that: examples. DepCharge is designed to be as flexible as possible, so if you happen to use tools other than what's listed, they should work as well!
Usage: depcharge [version] [--help|-h] [--dryrun|-d] [--force|-f] [--kind|-k=<kind>] [--instead|-x=<action>] [[--include|-i][-e|--exclude]] [--labels|-l=<comma-separated,inherited>] [--serial|-s] -- COMMAND [ARGS...]
Features:
- Built-in mustache templating, allows you to parametrize your commands
- Supports arbitrary params in YAML, whatever 'params: key: value' pairs you want (particularly useful for mustache templating)
- Supports YAML anchors
- Even went the extra mile to support anchors + sequence merging via
merge-deps:
(see:YAML Anchors & Sequences
)
- Even went the extra mile to support anchors + sequence merging via
Description:
depcharge
will read the dep.yml
file in the current working directory, and
perform all commands relative to that location.
Example dep.yml
:
deps:
- name: frontend
kind: git
location: ./app/frontend
labels:
- public
params:
repo: [email protected]:frontend.git
deps:
- name: vue.js
kind: npm
- name: backend
kind: git
location: ./app/backend
labels:
- api
params:
repo: [email protected]:backend.git
deps:
- name: lumen
kind: composer
Flags
--version Displays the program version string.
-h --help Displays help with available flag, subcommand, and positional value parameters.
-d --dryrun Will print out the command to be run, does not make changes to your system.
-e --exclusive Applies labels in an exclusive way (default).
-f --force Will force-run a command without confirmations, could be dangerous.
-i --inclusive Applies labels in an inclusive way.
-k --kind Targets specific kinds of dependencies (i.e. git, npm, composer)
-l --labels Filters to specific labels.
-s --serial Prevents parallel execution, runs commands one at a time.
-x --instead Instead of 'kind', perform a different command.
Example commands:
Will run git clone <repo> <location>
across all git dependencies:
depcharge --kind=git -- clone {{repo}} {{location}}
Or, shorthand:
depcharge -- git clone {{repo}} {{location}}
Will run git status
across all git dependencies:
depcharge -- git status
Will run npm install
across any npm dependencies that have the label 'public':
depcharge --labels=public -- npm install
Will run composer install
across any composer dependencies that have either the label 'api', or 'soap':
depcharge --inclusive --labels=api,soap -- composer install
And much more!
YAML Anchors & Sequences
Due to a limitation in YAML itself, you cannot use anchors to merge sequences (arrays). Therefore this is programatically supported within DepCharge.
Invalid YAML, you cannot mix sequences -
with anchors *<name>
directly, this doesn't work:
...
deps:
- kind: git
- *composer
- *vue
...
It's a beautiful concept though, that really helps with reusability and simplifies the overall YAML file, and so merge-deps
was introduced to work around this shortcoming.
Working around this with merge-deps:
.vue: &vue
- name: Vue.js
kind: npm
.composer: &composer
- name: lumen
kind: composer
deps:
- name: ui
kind: project
location: ./code/app
labels:
- ui
deps:
- kind: git
params:
repo: [email protected]/ui.git
merge-deps:
- *composer
- *vue
In the above example, merge-deps:
supports listing your anchors, and these will then be expanded, then flattened and merged into deps:
before final processing begins.
Special Action Handlers
DepCharge has the ability to offer special-case action handlers. Specifically for situations where executing bulk commands cause difficulties and/or there are unexpected rough edges.
git clone
This is treated specially, in the sense that a regular clone will not act if parent directories aren't already in place. DepCharge will detect theclone
action explicitly and attempt to create any parent directories before passing the command directly ontogit
Additional Resources
Contributing
See: [CONTRIBUTING.md](CONTRIBUTING.md)
License
- [LICENSE](LICENSE) (Expat/MIT License)
*Note that all licence references and agreements mentioned in the DepCharge README section above
are relevant to that project's source code only.