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
[](https://quay.io/repository/drycc/postgres)
8
8
9
-
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/teamhephy/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
-
This component is a PostgreSQL database for use in Kubernetes. It builds on the official [postgres](https://registry.hub.docker.com/_/postgres/) Docker image. While it's intended for use inside of the Deis Workflow 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 or even as a standalone Docker container.
17
+
This component is a PostgreSQL database for use in Kubernetes. It builds on the official [postgres](https://registry.hub.docker.com/_/postgres/) Docker image. While it's intended for use inside of the Drycc Workflow 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 or even as a standalone Docker container.
18
18
19
19
# Development
20
20
21
-
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.
21
+
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.
22
22
23
23
- Fork this repository
24
24
- Make your changes
25
25
- Submit a [pull request][prs] (PR) to this repository with your changes, and unit tests whenever possible
26
26
- 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)
27
-
- 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
27
+
- 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
28
28
29
29
## Prerequisites
30
30
31
-
In order to develop and test this component in a Deis cluster, you'll need the following:
31
+
In order to develop and test this component in a Drycc cluster, you'll need the following:
32
32
33
33
*[GNU Make](https://www.gnu.org/software/make/)
34
34
*[Docker](https://www.docker.com/) installed, configured and running
@@ -37,27 +37,27 @@ In order to develop and test this component in a Deis cluster, you'll need the f
37
37
38
38
## Testing Your Code
39
39
40
-
Once you have all the aforementioned prerequisites, you are ready to start writing code. Once you've finished building a new feature or fixed a bug, please write a unit or integration test for it if possible. See [an existing test](https://github.com/teamhephy/postgres/blob/master/contrib/ci/test.sh) for an example test.
40
+
Once you have all the aforementioned prerequisites, you are ready to start writing code. Once you've finished building a new feature or fixed a bug, please write a unit or integration test for it if possible. See [an existing test](https://github.com/drycc/postgres/blob/master/contrib/ci/test.sh) for an example test.
41
41
42
-
If your feature or bugfix doesn't easily lend itself to unit/integration testing, you may need to add tests at a higher level. Please consider adding a test to our [end-to-end test suite](https://github.com/teamhephy/workflow-e2e) in that case. If you do, please reference the end-to-end test pull request in your pull request for this repository.
42
+
If your feature or bugfix doesn't easily lend itself to unit/integration testing, you may need to add tests at a higher level. Please consider adding a test to our [end-to-end test suite](https://github.com/drycc/workflow-e2e) in that case. If you do, please reference the end-to-end test pull request in your pull request for this repository.
43
43
44
44
### Dogfooding
45
45
46
46
Finally, we encourage you to [dogfood](https://en.wikipedia.org/wiki/Eating_your_own_dog_food) this component while you're writing code on it. To do so, you'll need to build and push Docker images with your changes.
47
47
48
-
This project has a [Makefile](https://github.com/teamhephy/postgres/blob/master/Makefile) that makes these tasks significantly easier. It requires the following environment variables to be set:
48
+
This project has a [Makefile](https://github.com/drycc/postgres/blob/master/Makefile) that makes these tasks significantly easier. It requires the following environment variables to be set:
49
49
50
-
*`DEIS_REGISTRY` - A Docker registry that you have push access to and your Kubernetes cluster can pull from
50
+
*`DRYCC_REGISTRY` - A Docker registry that you have push access to and your Kubernetes cluster can pull from
51
51
* If this is [Docker Hub](https://hub.docker.com/), leave this variable empty
52
52
* Otherwise, ensure it has a trailing `/`. For example, if you're using [Quay.io](https://quay.io), use `quay.io/`
53
-
*`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.
53
+
*`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.
54
54
*`SHORT_NAME` (optional) - The name of the image. This defaults to `postgres`
55
55
*`VERSION` (optional) - The tag of the Docker image. This defaults to the current Git SHA (the output of `git rev-parse --short HEAD`)
56
56
57
57
Assuming you have these variables set correctly, run `make docker-build` to build the new image, and `make docker-push` to push it. Here is an example command that would push to `quay.io/arschles/postgres:devel`:
58
58
59
59
```console
60
-
export DEIS_REGISTRY=quay.io/
60
+
export DRYCC_REGISTRY=quay.io/
61
61
export IMAGE_PREFIX=arschles
62
62
export VERSION=devel
63
63
make docker-build docker-push
@@ -66,7 +66,7 @@ make docker-build docker-push
66
66
Note that you'll have to push your image to a Docker repository (`make docker-push`) in order for your Kubernetes cluster to pull the image. This is important for testing in your cluster.
0 commit comments