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: docs/development-guide.md
+1-3
Original file line number
Diff line number
Diff line change
@@ -61,9 +61,7 @@ The input variables, with their default values (some auto generated) are:
61
61
-`smtp_emails_from_email`: The email account to use as the sender in the notification emails, it could be something like `info@your-custom-domain.com`.
62
62
-`smtp_emails_from_name`: The email account name to use as the sender in the notification emails, it could be something like `Symona Adaro`.
63
63
-`smtp_emails_to_email`: The email account to use as the recipient for `contact us` emails, it could be something like `requests@your-custom-domain.com`.
64
-
-`mongo_host`: MongoDB host cluster URI password
65
-
-`mongo_user`: MongoDB User account to access the cluster
66
-
-`mongodb_password`: MongoDB password for access to the cluster
64
+
-`mongodb_uri`: MongoDB URI for access to the cluster
67
65
-`mongodb_database`: MongoDB database to have the application operate within
68
66
-`traefik_constraint_tag`: The tag to be used by the internal Traefik load balancer (for example, to divide requests between backend and frontend) for production. Used to separate this stack from any other stack you might have. This should identify each stack in each environment (production, staging, etc).
69
67
-`traefik_constraint_tag_staging`: The Traefik tag to be used while on staging.
Copy file name to clipboardExpand all lines: docs/getting-started.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ Running Cookiecutter to customise the deployment with your settings, and then bu
83
83
84
84
### Setting up a Mongo Connection
85
85
86
-
A Mongo connection can be set up one of two ways: At the cookiecutter generation step, provide the `mongo_host`, `mongo_user`, `mongo_password`, and `mongo_database` to inform the generator on how to connect to an Atlas cloud instance. Additionally, in the generated file, you can manually set the .env.MONGO_DATABASE_URI and it will connect to the Atlas cluster made locally.
86
+
A Mongo connection can be set up one of two ways: At the cookiecutter generation step, provide the `mongodb_uri`, and `mongo_database` to inform the generator on how to connect to an Atlas cloud instance. Additionally, in the generated file, you can manually set the .env.MONGO_DATABASE_URI and it will connect to the Atlas cluster made locally.
87
87
88
88
Additionally, developers could configure a local mongo instance, but it would either have to be spun up in docker, or generated separately and also allow for non-localhost connections to be made.
0 commit comments