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: cmd/cloudx/proxy/proxy.go
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -68,9 +68,9 @@ Per default, CORS is enabled for all origins.
68
68
69
69
### Connecting in automated environments
70
70
71
-
To connect the Ory Tunnel in automated environments, create a Project API Key for your project and set it as an environment variable:
71
+
To connect the Ory Tunnel in automated environments, create a Project API Key for your project, set it as an environment variable, and use the `+"`--quiet`"+` flag:
Note: You cannot set a path in the `+"`publish-url`"+`.
86
86
@@ -95,18 +95,18 @@ By default, the proxy listens on port 4000. To change this, use the ` + "`--port
95
95
If the proxy runs on a subdomain and you want Ory’s cookies (e.g., session cookies) to be accessible across all your domains, use the `+"`--cookie-domain`"+` flag to customize the cookie domain. Additionally, allow your subdomains in the CORS headers:
This ensures that all redirects (e.g., after login) go to `+"`/welcome`"+` instead of `+"`/`"+`, unless you’ve specified custom redirects in your Ory configuration or via the flow’s `+"`?return_to=`"+` query parameter.
To connect the Ory Tunnel in automated environments, create a Project API Key for your project and set it as an environment variable:
53
+
To connect the Ory Tunnel in automated environments, create a Project API Key for your project, set it as an environment variable, and use the `+"`--quiet`"+` flag:
0 commit comments