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
Copy file name to clipboardExpand all lines: README.md
+11-14Lines changed: 11 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,19 +78,13 @@ We are releasing an alpha version, which may miss some necessary features.
78
78
79
79
## Deploying in Google Cloud Platform (GCP)
80
80
### Defining environment variables
81
-
First, determine whether there are multiple developers deploying simultaneously in your environment. If yes, use the multiple users template, otherwise use the single user template.
81
+
First, copy the example environment variables template to the existing directory.
82
82
```
83
-
# multiple users
84
-
cp .env.multiusers env.bzl
85
-
```
86
-
```
87
-
# single user
88
-
cp .env.singleuser env.bzl
83
+
cp .env.example env.bzl
89
84
```
90
85
Edit the variables in `env.bzl`. The `env.bzl` file is the one that really takes effect, the other files are just templates. The double quotes around a variable name are needed. For example:
91
86
```
92
87
env="dev" # the deployment environment
93
-
username="mock developer name" # the developer name
94
88
mysql_username="mockname" # mysql database username
95
89
mysql_password="mockpwd" # mysql database password
96
90
project_id="you project id" # gcp project id
@@ -102,17 +96,20 @@ zone="" # the zone that the resources created in
102
96
### Preparing resources
103
97
Create resources for the data clean room by terraform. Make sure you have correctly defined environment variables in the `env.bzl`.
104
98
105
-
`resources/gcp` directory contains the resources releated to the gcp including: clusters, cloud sql instance, database, docker repositories, and service accounts. These resource are global and only created once for all the developers in one project.
106
-
107
-
`resources/kubernetes` directory includes the resources releated to the kubernete cluster including: namespace, role, secret.
108
-
109
-
Create all the resources by:
99
+
`resources/gcp` directory contains the resources releated to the gcp including: clusters, cloud sql instance, database, docker repositories, and service accounts. These resource are global and only created once for all the developers in one project. If you are the project owner, run the commands to create global resources.
110
100
```
111
-
pushd resources
101
+
pushd resources/gcp
112
102
./apply.sh
113
103
popd
114
104
```
115
105
106
+
`resources/kubernetes` directory includes the resources releated to the kubernete cluster including: namespace, role, secret. Once the global resources have been created, the developers can run the commands to create user-specific resources. The namespace is required, and make sure the namespace is distinct.
107
+
```
108
+
pushd resources/kubernetes
109
+
./apply.sh --namespace=xxxx
110
+
popd
111
+
```
112
+
116
113
### Building and Pushing Images
117
114
`app` directory contains the source codes of the data clean room which has three components:
0 commit comments