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
If your change requires any additions or changes to the [documentation][docs] or to the [end-to-end test suite][e2e], please submit them as 1 or more pull requests against that repo and refer to them here.
[](https://quay.io/repository/deisci/controller)
[](https://quay.io/repository/drycc/controller)
Deis (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any [Kubernetes](http://kubernetes.io) cluster, making it easy to deploy and manage applications on your own servers.
9
+
Drycc (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any [Kubernetes](http://kubernetes.io) cluster, making it easy to deploy and manage applications on your own servers.
10
10
11
-
For more information about the Deis Workflow, please visit the main project page at https://github.com/deisthree/workflow.
11
+
For more information about the Drycc Workflow, please visit the main project page at https://github.com/drycc/workflow.
12
12
13
13
We welcome your input! If you have feedback, please [submit an issue][issues]. If you'd like to participate in development, please read the "Development" section below and [submit a pull request][prs].
14
14
15
15
# About
16
16
17
-
The Controller is the central API server for [Deis Workflow][workflow]. It is installed on a [Kubernetes](http://kubernetes.io) cluster, making it easy to deploy and manage applications on your own cluster. Below is a non-exhaustive list of things it can do:
17
+
The Controller is the central API server for [Drycc Workflow][workflow]. It is installed on a [Kubernetes](http://kubernetes.io) cluster, making it easy to deploy and manage applications on your own cluster. Below is a non-exhaustive list of things it can do:
18
18
19
19
* Create a new application
20
20
* Delete an application
@@ -24,13 +24,13 @@ The Controller is the central API server for [Deis Workflow][workflow]. It is in
24
24
25
25
# Development
26
26
27
-
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.
27
+
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.
28
28
29
29
* Fork this repository
30
30
* Make your changes
31
31
*[Submit a pull request][prs] (PR) to this repository with your changes, and unit tests whenever possible.
32
32
* 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)
33
-
*Deis project maintainers will review your code.
33
+
*Drycc project maintainers will review your code.
34
34
* After two maintainers approve it, they will merge your PR.
35
35
36
36
## Prerequisites
@@ -47,38 +47,38 @@ You'll want to test your code changes interactively in a working Kubernetes clus
47
47
48
48
### Workflow Installation
49
49
50
-
After you have a working Kubernetes cluster, you're ready to [install Workflow](https://deis.com/docs/workflow/installing-workflow/).
50
+
After you have a working Kubernetes cluster, you're ready to [install Workflow](https://drycc.com/docs/workflow/installing-workflow/).
51
51
52
52
## Testing Your Code
53
53
54
54
When you've built your new feature or fixed a bug, make sure you've added appropriate unit tests and run `make test` to ensure your code works properly.
55
55
56
56
Also, since this component is central to the platform, it's recommended that you manually test and verify that your feature or fix works as expected. To do so, ensure the following environment variables are set:
57
57
58
-
*`DEIS_REGISTRY` - A Docker registry that you have push access to and your Kubernetes cluster can pull from
58
+
*`DRYCC_REGISTRY` - A Docker registry that you have push access to and your Kubernetes cluster can pull from
59
59
* If this is [Docker Hub](https://hub.docker.com/), leave this variable empty
60
60
* Otherwise, ensure it has a trailing `/`. For example, if you're using [Quay.io](https://quay.io), use `quay.io/`
61
-
*`IMAGE_PREFIX` - The organization in the Docker repository. This defaults to `deis`, but if you don't have access to that organization, set this to one you have push access to.
61
+
*`IMAGE_PREFIX` - The organization in the Docker repository. This defaults to `drycc`, but if you don't have access to that organization, set this to one you have push access to.
62
62
*`SHORT_NAME` (optional) - The name of the image. This defaults to `controller`
63
63
*`VERSION` (optional) - The tag of the Docker image. This defaults to the current Git SHA (the output of `git rev-parse --short HEAD`)
64
64
65
65
Then, run `make deploy` to build and push a new Docker image with your changes and replace the existing one with your new one in the Kubernetes cluster. See below for an example with appropriate environment variables.
66
66
67
67
```console
68
-
export DEIS_REGISTRY=quay.io/
68
+
export DRYCC_REGISTRY=quay.io/
69
69
export IMAGE_PREFIX=arschles
70
70
make deploy
71
71
```
72
72
73
73
After the `make deploy` finishes, a new pod will be launched but may not be running. You'll need to wait until the pod is listed as `Running` and the value in its `Ready` column is `1/1`. Use the following command watch the pod's status:
74
74
75
75
```console
76
-
kubectl get pod --namespace=deis -w | grep deis-controller
76
+
kubectl get pod --namespace=drycc -w | grep drycc-controller
0 commit comments