Skip to content

Commit ce00e29

Browse files
committed
Merge branch 'master' of github.com:doitintl/iris3
2 parents ed85fd7 + 2fa3cc8 commit ce00e29

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,7 @@ names start `_gcp_`. The part of the function name after `_gcp_` is used for the
8888
* You can deploy Iris in any project within your Google Cloud organization, but we recommend using a
8989
[new project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project).
9090

91+
9192
### Needed roles for deployment
9293
#### Organization-level roles
9394

@@ -105,7 +106,7 @@ names start `_gcp_`. The part of the function name after `_gcp_` is used for the
105106

106107
* Fine-granted "predefined roles" are not possible because deploying Cloud Scheduler cron requires at least Editor or Owner, per GCP docs.
107108

108-
### App Engine Defaults
109+
109110

110111
## Deployment
111112

@@ -119,7 +120,7 @@ names start `_gcp_`. The part of the function name after `_gcp_` is used for the
119120
* Set up the configuration
120121
* Copy `config.yaml.original` to `config.yaml`.
121122
* Optionally configure by editing the config file. ([See more documentation below](#configuration).)
122-
123+
* As always with App Engine, a default service must exist before any other exists. So if you are working with a new project, create a simple Hello World App Engine service to fulfil that App Engine requirement.
123124
* Now, run `./deploy.sh <PROJECT_ID> `.
124125
* For documentation on usage of command-line options, run `deploy.sh -h`
125126

@@ -173,4 +174,4 @@ names start `_gcp_`. The part of the function name after `_gcp_` is used for the
173174
# Development and Testing
174175

175176
Please see [README_for_dev_and_testing](./README_for_dev_and_testing.md)
176-
177+

0 commit comments

Comments
 (0)