Skip to content

Latest commit

 

History

History
39 lines (25 loc) · 2.89 KB

README.md

File metadata and controls

39 lines (25 loc) · 2.89 KB
Deis Workflow will soon no longer be maintained.
Please read the announcement for more detail.
09/07/2017 Deis Workflow v2.18 final release before entering maintenance mode
03/01/2018 End of Workflow maintenance: critical patches no longer merged

Hephy Slugbuilder v2

Build Status Docker Repository on Quay

Deis (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any Kubernetes cluster, making it easy to deploy and manage applications on your own servers.

For more information about the Deis Workflow, please visit the main project page at https://github.com/teamhephy/workflow.

We welcome your input! If you have feedback, please submit an issue. If you'd like to participate in development, please read the "Development" section below and submit a pull request.

About

The slugbuilder downloads a git archive (gzipped tarball) from a specified S3 API compatible server, compiles a slug and uploads it to a specified S3 API compatible server.

This component is usually launched by the Deis Builder and used inside the Deis PaaS, but it is flexible enough to be used as a pod inside any Kubernetes cluster.

Please see https://github.com/teamhephy/builder/blob/master/README.md for a more detailed description of how slugbuilder interacts with builder.

Development

The Deis project welcomes contributions from all developers. The high level process for development matches many other open source projects. See below for an outline.

  • Fork this repository
  • Make your changes
  • Submit a pull request (PR) to this repository with your changes, and unit tests whenever possible.
    • If your PR fixes any issues, make sure you write Fixes #1234 in your PR description (where #1234 is the number of the issue you're closing)
  • The Deis core contributors will review your code. After each of them sign off on your code, they'll label your PR with LGTM1 and LGTM2 (respectively). Once that happens, the contributors will merge it