Drycc (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 Drycc Workflow, please visit the main project page at https://github.com/drycc/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.
The Imagebuilder downloads a git archive (gzipped tarball) from a specified [S3 API compatible server][s3-api] and runs docker build on it. When the build is done, it runs docker push to push the resulting image to a specified Docker repository.
This component is usually launched by the Drycc Builder and used inside the Drycc PaaS, but it is flexible enough to be used as a pod inside any Kubernetes cluster.
The Drycc 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 Drycc 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