Hephy - A Fork of Deis Workflow
Hephy (pronounced HEF-ee) 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 Hephy 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.
The builder is primarily a git server that responds to git push
es by executing either the git-receive-pack
or git-upload-pack
hook. After it executes one of those hooks, it takes the following high level steps in order:
git archive
to produce a tarball (i.e. a .tar.gz
file) on the local file systemBUILDER_STORAGE
environment variable is other than minio
, attempts to create the appropriate storage driver and saves using this driver.BUILDER_STORAGE
is minio
and the DEIS_MINIO_SERVICE_HOST
and DEIS_MINIO_SERVICE_PORT
environment variables exist (these are standard Kubernetes service discovery environment variables), saves to the S3 API compatible server at http://$DEIS_MINIO_SERVICE_HOST:$DEIS_MINIO_SERVICE_HOST
Dockerfile
is present in the codebase, starts a dockerbuilder
pod, configured to download the code to build from the URL computed in the previous step.slugbuilder
pod, configured to download the code to build from the URL computed in the previous step.Builder currently supports the following off-cluster storage backends:
The Hephy project welcomes contributions from all developers. The high level process for development matches many other open source projects. See below for an outline.
Fixes #1234
in your PR description (where #1234
is the number of the issue you're closing)LGTM1
and LGTM2
(respectively). Once that happens, a contributor will merge itThe preferred environment for development uses the go-dev
Docker image. The tools described in this section are used to build, test, package and release each version of Hephy.
To use it yourself, you must have make installed and Docker installed and running on your local development machine.
If you don't have Docker installed, please go to https://www.docker.com/ to install it.
After you have those dependencies, grab Go dependencies with make bootstrap
, build your code with make build
and execute unit tests with make test
.
You can also use the standard go
toolchain to build and test if you prefer. To do so, you'll need glide 0.9 or above and Go 1.6 or above installed.
After you have those dependencies, you can build and unit-test your code with go build
and go test $(glide nv)
, respectively.
Note that you will not be able to build or push Docker images using this method of development.
The Hephy project requires that as much code as possible is unit tested, but the core contributors also recognize that some code must be tested at a higher level (functional or integration tests, for example).
The end-to-end tests repository has our integration tests. Additionally, the core contributors and members of the community also regularly dogfood the platform. Since this particular component is at the center of much of the Hephy Workflow platform, we find it especially important to dogfood it.
Please see README.md on the end-to-end tests repository for instructions on how to set up your testing environment and run the tests.
Please follow the instructions on the official Deis docs to install and configure your Deis Workflow cluster and all related tools, and deploy and configure an app on Deis Workflow.