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
||Deis Workflow will soon no longer be maintained.<br />Please [read the announcement](https://deis.com/blog/2017/deis-workflow-final-release/) for more detail. |
2
+
||Drycc Workflow will soon no longer be maintained.<br />Please [read the announcement](https://drycc.com/blog/2017/drycc-workflow-final-release/) for more detail. |
3
3
|---:|---|
4
-
| 09/07/2017 |Deis Workflow [v2.18][] final release before entering maintenance mode |
4
+
| 09/07/2017 |Drycc Workflow [v2.18][] final release before entering maintenance mode |
5
5
| 03/01/2018 | End of Workflow maintenance: critical patches no longer merged |
[](https://quay.io/repository/deisci/registry)
[](https://quay.io/repository/drycc/registry)
12
12
13
13
14
-
Deis (pronounced DAY-iss) is an open source PaaS that makes it easy to deploy and manage
15
-
applications on your own servers. Deis builds on [Kubernetes](http://kubernetes.io/) to provide
14
+
Drycc (pronounced DAY-iss) is an open source PaaS that makes it easy to deploy and manage
15
+
applications on your own servers. Drycc builds on [Kubernetes](http://kubernetes.io/) to provide
16
16
a lightweight, [Heroku-inspired](http://heroku.com) workflow.
17
17
18
18
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].
19
19
20
20
# About
21
21
22
-
The registry is a [Docker registry](https://docs.docker.com/registry/) component for use in Kubernetes. While it's intended for use inside of the Deis open source [PaaS](https://en.wikipedia.org/wiki/Platform_as_a_service), it's flexible enough to be used as a standalone pod on any Kubernetes cluster.
22
+
The registry is a [Docker registry](https://docs.docker.com/registry/) component for use in Kubernetes. While it's intended for use inside of the Drycc open source [PaaS](https://en.wikipedia.org/wiki/Platform_as_a_service), it's flexible enough to be used as a standalone pod on any Kubernetes cluster.
23
23
24
24
If you decide to use this component standalone, you can host your own Docker registry in your own Kubernetes cluster.
25
25
26
26
The Docker image that this repository builds is based on [the official Docker v2 registry image](https://github.com/docker/distribution).
27
27
28
28
# Development
29
29
30
-
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.
30
+
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.
31
31
32
32
* Fork this repository
33
33
* Make your changes
34
34
* Submit a pull request (PR) to this repository with your changes, and unit tests whenever possible.
35
35
* 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)
36
-
* 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
36
+
* 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
37
37
38
38
## Deploying
39
39
40
-
If you want to use the latest registry image built by they Deis team you can simply start a registry via `make deploy`.
40
+
If you want to use the latest registry image built by they Drycc team you can simply start a registry via `make deploy`.
41
41
42
42
If however, you want to build and use a custom image see the instructions below.
43
43
@@ -49,7 +49,7 @@ To build a dev release of this image, you will also need a registry to hold the
49
49
First, configure your environment to point to the registry location.
50
50
51
51
```console
52
-
$ exportDEIS_REGISTRY=myregistry.com:5000 # or quay.io, if using Dockerhub, leave this unset
52
+
$ exportDRYCC_REGISTRY=myregistry.com:5000 # or quay.io, if using Dockerhub, leave this unset
53
53
$ export IMAGE_PREFIX=youruser/ # if using Quay or Dockerhub
54
54
```
55
55
@@ -65,6 +65,6 @@ To deploy the image via patching the registry deployment run:
0 commit comments