You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
||Hephy Workflow is the open source fork of Deis Workflow.<br />Please [read the announcement][] for more detail. |
2
+
||Drycc Workflow is the open source fork of Drycc Workflow.<br />Please [read the announcement][] for more detail. |
3
3
|---:|---|
4
-
| 11/29/2018 |Hephy Workflow [v2.20.0][] new release |
5
-
| 08/27/2018 | Team Hephy[blog][] comes online |
6
-
| 08/20/2018 |Deis[#community slack][] goes dark |
**Deis Workflow** is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any [Kubernetes][k8s-home] cluster, making it easy to deploy and manage applications.
19
+
**Drycc Workflow** is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any [Kubernetes][k8s-home] cluster, making it easy to deploy and manage applications.
20
20
21
-
Deis Workflow is the second major release (v2) of the Deis PaaS. If you are looking for the CoreOS-based PaaS visit [https://github.com/deis/deis](https://github.com/deis/deis).
21
+
Drycc Workflow is the second major release (v2) of the Drycc PaaS. If you are looking for the CoreOS-based PaaS visit [https://github.com/drycc/drycc](https://github.com/drycc/drycc).
22
22
23
-
To **get started** with **Deis Workflow** please read the [Quick Start Guide](https://deis.com/docs/workflow/quickstart/).
23
+
To **get started** with **Drycc Workflow** please read the [Quick Start Guide](https://drycc.com/docs/workflow/quickstart/).
24
24
25
-
Visit [https://deis.com](https://deis.com) for more information on [why you should use Deis Workflow](https://deis.com/why-deis/) or [learn about its features](https://deis.com/how-it-works/).
25
+
Visit [https://drycc.com](https://drycc.com) for more information on [why you should use Drycc Workflow](https://drycc.com/why-drycc/) or [learn about its features](https://drycc.com/how-it-works/).
26
26
27
-
This repository contains the source code for Deis Workflow documentation. If you're looking for individual components, they live in their own repositories.
27
+
This repository contains the source code for Drycc Workflow documentation. If you're looking for individual components, they live in their own repositories.
28
28
29
29
Please see below for links and descriptions of each component:
30
30
31
-
-[controller](https://github.com/teamhephy/controller) - Workflow API server
32
-
-[builder](https://github.com/teamhephy/builder) - Git server and source-to-image component
33
-
-[dockerbuilder](https://github.com/teamhephy/dockerbuilder) - The builder for [Docker](https://www.docker.com/) based applications
34
-
-[slugbuilder](https://github.com/teamhephy/slugbuilder) - The builder for [slug/buildpack](https://devcenter.heroku.com/articles/slug-compiler) based applications
35
-
-[slugrunner](https://github.com/teamhephy/slugrunner) - The runner for slug/buildpack based applications
36
-
-[fluentd](https://github.com/teamhephy/fluentd) - Backend log shipping mechanism for `deis logs`
37
-
-[postgres](https://github.com/teamhephy/postgres) - The central database
38
-
-[registry](https://github.com/teamhephy/registry) - The Docker registry
39
-
-[logger](https://github.com/teamhephy/logger) - The (in-memory) log buffer for `deis logs`
40
-
-[monitor](https://github.com/teamhephy/monitor) - The platform monitoring components
41
-
-[router](https://github.com/teamhephy/router) - The HTTP/s edge router
42
-
-[minio](https://github.com/teamhephy/minio) - The in-cluster, ephemeral, development-only object storage system
-[workflow-e2e](https://github.com/teamhephy/workflow-e2e) - End-to-end tests for the entire platform
46
-
-[workflow-manager](https://github.com/teamhephy/workflow-manager) - Manage, inspect, and debug a Workflow cluster
31
+
-[controller](https://github.com/drycc/controller) - Workflow API server
32
+
-[builder](https://github.com/drycc/builder) - Git server and source-to-image component
33
+
-[dockerbuilder](https://github.com/drycc/dockerbuilder) - The builder for [Docker](https://www.docker.com/) based applications
34
+
-[slugbuilder](https://github.com/drycc/slugbuilder) - The builder for [slug/buildpack](https://devcenter.heroku.com/articles/slug-compiler) based applications
35
+
-[slugrunner](https://github.com/drycc/slugrunner) - The runner for slug/buildpack based applications
36
+
-[fluentd](https://github.com/drycc/fluentd) - Backend log shipping mechanism for `drycc logs`
37
+
-[postgres](https://github.com/drycc/postgres) - The central database
38
+
-[registry](https://github.com/drycc/registry) - The Docker registry
39
+
-[logger](https://github.com/drycc/logger) - The (in-memory) log buffer for `drycc logs`
40
+
-[monitor](https://github.com/drycc/monitor) - The platform monitoring components
41
+
-[router](https://github.com/drycc/router) - The HTTP/s edge router
42
+
-[minio](https://github.com/drycc/minio) - The in-cluster, ephemeral, development-only object storage system
-[workflow-e2e](https://github.com/drycc/workflow-e2e) - End-to-end tests for the entire platform
46
+
-[workflow-manager](https://github.com/drycc/workflow-manager) - Manage, inspect, and debug a Workflow cluster
47
47
48
48
We welcome your input! If you have feedback, please [submit an issue][issues]. If you'd like to participate in development, please read the "Working on Documentation" section below and [submit a pull request][prs].
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.
55
+
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.
56
56
57
57
* Fork this repository.
58
58
* Make your changes.
59
59
*[Submit a pull request][prs] (PR) to this repository with your changes, and unit tests whenever possible.
60
60
* If your PR fixes any [issues][issues], make sure you write `Fixes #1234` in your PR description (where `#1234` is the number of the issue you're closing).
61
-
* 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, a contributor will merge it.
61
+
* 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, a contributor will merge it.
62
62
63
63
## Requirements
64
64
@@ -85,14 +85,14 @@ Then view the documentation on [http://localhost:8000](http://localhost:8000) or
0 commit comments