|
|
@@ -8,7 +8,7 @@
|
|
|
|
|
|
Traditional PaaS's like Heroku are great at minimizing unnecessary DevOps work but don't offer enough flexibility as your applications scale. Custom network rules, resource constraints, and cost are common reasons developers move their application off Heroku beyond a certain scale.
|
|
|
|
|
|
-Porter brings the simplicity of traditional PaaS's to your own cloud provider while preserving the full configurability of Kubernetes. It's built on top of a popular Kubernetes framework called Helm and is compatible with standard Kubernetes management tools like `kubectl`, preparing your infra for mature DevOps work from day 1.
|
|
|
+Porter brings the simplicity of traditional PaaS's to your own cloud provider while preserving the configurability of Kubernetes. It's built on top of a popular Kubernetes framework called Helm and is compatible with standard Kubernetes management tools like `kubectl`, preparing your infra for mature DevOps work from day 1.
|
|
|
|
|
|

|
|
|
|
|
|
@@ -18,21 +18,25 @@ Porter brings the simplicity of traditional PaaS's to your own cloud provider wh
|
|
|
- ✅ AWS
|
|
|
- 🚧 GCP
|
|
|
- 🚧 Digital Ocean
|
|
|
-- Simple deploy of any Docker image (public or private)
|
|
|
+
|
|
|
+
|
|
|
+
|
|
|
+- Simple deploy of any public or private Docker image
|
|
|
+
|
|
|
- Heroku-like GUI to monitor application status, logs, and history
|
|
|
- Marketplace for 1-click add-on's (e.g. MongoDB, Redis, PostgreSQL)
|
|
|
- Application rollback to previous deploy versions
|
|
|
- Native CI/CD with buildpacks (Coming Soon)
|
|
|
|
|
|
-
|
|
|
-
|
|
|
### DevOps Mode
|
|
|
For those who are familiar with Kubernetes and Helm:
|
|
|
+
|
|
|
- Visualize, deploy and configure Helm charts via the GUI
|
|
|
+
|
|
|
- User-generated [form overlays](https://docs.getporter.dev/docs/porter-templates) for managing `values.yaml`
|
|
|
- In-depth view of releases, including revision histories and component graphs
|
|
|
- Rollback/update of existing releases, including editing of raw `values.yaml`
|
|
|
-- Connect to and manage existing Kubernetes clusters that are not provisioned by Porter
|
|
|
+- Connect to existing Kubernetes clusters that are not provisioned by Porter
|
|
|
|
|
|

|
|
|
|
|
|
@@ -62,7 +66,7 @@ For Linux and Windows installation, see our [Docs](https://docs.getporter.dev/do
|
|
|
## Getting Started
|
|
|
1. Sign up and log into [Porter Dashboard](https://dashboard.getporter.dev).
|
|
|
|
|
|
-2. Create a Project and select a cloud provider you want to run a Kubernetes cluster in.
|
|
|
+2. Create a Project and select a cloud provider you want to provision a Kubernetes cluster in.
|
|
|
|
|
|
3. Put in your credentials, then Porter will automatically provision a cluster and an image registry in your own cloud account.
|
|
|
|
|
|
@@ -71,4 +75,3 @@ For Linux and Windows installation, see our [Docs](https://docs.getporter.dev/do
|
|
|
5. From the Templates tab on the Dashboard, select the Docker template. Click on the image you have just pushed, configure the port, then hit deploy.
|
|
|
|
|
|

|
|
|
-
|