Package your application artifact, client tools, configuration and deployment logic together as a versioned bundle that you can distribute, and then install with a single command. Based on the Cloud Native Application Bundle Specification, CNAB, Porter provides a declarative authoring experience that lets you focus on what you know best: your application.
Learn all about Porter at porter.sh
Mixins provide out-of-the-box support for interacting with different tools and services from inside a bundle. You can always create a mixin, or use the exec mixin and a Custom Dockerfile if a custom mixin doesn't exist yet.
Porter Mixins are available for below platform's:
Plugins let you store Porter's data and retrieve secrets from an external service.
Porter Plugins are available for below platform's:
- Mailing List - Great for following the project at a high level because it is low traffic, mostly release notes and blog posts on new features.
- Forum - Share an idea or propose a design where everyone can benefit from the discussion and find answers to questions later.
- Dev Meeting - Biweekly meeting where we discuss Porter Enhancement Proposals, demo new features and help other contributors.
- Open an Issue - If you are having trouble or found a bug, ask on GitHub so that we can prioritize it and make sure you get an answer.
- Slack - We have a #porter channel and there's also #cnab for deep thoughts about the CNAB specification.
Looking for Contributors
Want to work on Porter with us?
Start with our New Contributors Guide
Porter wouldn't be possible without our contributors, carrying
the load and making it better every day!
Do you use Porter?
We want to know if you use Porter! Project priorities and funding are based on adoption. So if you are using Porter, reply to this issue, or if it needs to stay private, email firstname.lastname@example.org.
Porter is an open-source project and things get done as quickly as we have
motivated contributors working on features that interest them.
We use a single project board across all of our repositories to track open issues and pull requests.
The roadmap represents what the maintainers have said that they are currently working on and plan to work on over the next few months. We use the "on-hold" bucket to communicate items of interest that do not have a maintainer who will be working on it.
Check out our roadmap
Our version strategy explains how we version the project, when you should expect breaking changes in a release, and the process for the v1 release.