Epinio

Opinionated platform that runs on Kubernetes to take you from Code to URL in one step.

What problem does Epinio solve?

Epinio makes it easy for developers to iterate on their applications running in Kubernetes. Easy means:

No experience with Kubernetes is required
No steep learning curve
Quick local setup with minimal configuration
Deploying to production similar to development

Kubernetes is becoming the de-facto standard for container orchestration. Developers may want to use Kubernetes for all the benefits it provides or may have to do so because that's what their Ops team has chosen. Whatever the case, using Kubernetes is not simple. It has a steep learning curve and doing it right is a full time job. Developers should spend their time working on their applications, not doing operations.

Epinio is adding the needed abstractions and intelligence to allow Developers to use Kubernetes as a PaaS (Platform as a Service).

Documentation

Detailed installation and user documentation is available at our main docs.epinio.io site.

Installation

The basic boilerplate requires a Kubernetes cluster, an Ingress Controller and a Cert Manager as detailed in the documentation. Once this is in place, and leaving out DNS setup, in the most trivial case the main installation boils down to

helm repo add epinio https://epinio.github.io/helm-charts
helm repo update

helm install --namespace epinio --create-namespace epinio epinio/epinio \                                               --set global.domain=mydomain.example.com

For the details glossed over here see the documentation.

Client installation

Installation of the Epinio CLI can be as simple as downloading a binary from the release page, or usage of brew, i.e.

brew install epinio

For the details glossed over here see the documentation.

Quick Start Tutorial

Our QuickStart Tutorial explains how to create a namespace and push an application.

Reach Us

Slack: #epinio on Rancher Users
Github: Discuss

Contributing

Epinio uses Github Project for tracking issues.

Find more information in the Contribution Guide.

Our developer documentation explains how to build and run Epinio from a source checkout.

Features

Security
- TLS secured API server
- Basic Authentication to access the API
- or OIDC-based token
Epinio Clients
- Web UI
- Epinio CLI
Apps
- Push code directly without additional tools or steps
- Basic operation of your application once pushed
- Cloud Native Buildpacks build and containerize your code for you
Configurations
- CRUD operations of your configuration. A configuration can be a database, SaaS etc. A configuration can be an external component or can be created using epinio configuration
- Bind configurations to apps

Example apps

Rails: https://github.com/epinio/example-rails
Java: https://github.com/spring-projects/spring-petclinic/
Paketo Buildpack example apps: https://github.com/paketo-buildpacks/samples

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

mmartin24/epinio_fork