autogen(docs): generate cli docs

Author: ory-bot

docs/cli/ory-proxy.md

@@ -20,35 +20,60 @@ This proxy works both in development and in production, for example when deployi
 React, NodeJS, Java, PHP, ... app to a server / the cloud or when developing it locally
 on your machine.
 
+The first argument `application-url` points to the location of your application. The Ory Proxy
+will pass all traffic through to this URL.
+
+    $ ory proxy --project <your-project-slug> https://www.example.org
+    $ ORY_PROJECT_SLUG=<your-project-slug> ory proxy http://localhost:3000
+
+### Connecting to Ory
+
 Before you start, you need to have a running Ory Cloud project. You can create one with the following command:
 
 	$ ory create project --name "Command Line Project"
 
-Pass the project's slug as a flag to the tunnel command:
+Pass the project's slug as a flag to the proxy command:
 
 	$ ory proxy --project <your-project-slug> ...
 	$ ORY_PROJECT_SLUG=<your-project-slug> ory proxy ...
 
-The first argument `app-url` points to the location of your application. If you are
-running the proxy and your app on the same host, this could be localhost.
+### Developing Locally
+
+When developing locally we recommend to use the `--dev` flag, which uses a lax security setting:
+
+	$ ory proxy --dev \
+		--project <your-project-slug> \
+		http://localhost:3000
 
-The second argument `[publish-url]` is optional. It refers to the public URL of your
-application (e.g. https://www.example.org).
+The first argument `application-url` points to the location of your application. If you are
+running the proxy and your app on the same host, this could be localhost. All traffic arriving at the
+Ory Proxy will be passed through to this URL.
+
+The second argument `[publish-url]` is optional and only needed when going to production.
+It refers to the public URL of your application (e.g. https://www.example.org).
 
 If `[publish-url]` is not set, it will default to the default
 host and port this proxy listens on:
 
 	http://localhost:4000
 
+### Running on a Server
+
+To go to production set up a custom domain (CNAME) for Ory. If you can not set up a custom
+domain - for example because you are developing a staging environment - using the Ory Proxy is an alternative.
+
 You must set the `[publish-url]` if you are not using the Ory Proxy in locally or in
 development:
 
-	$ ory proxy --project <your-project-slug> \
+	$ ory proxy \
+		--project <your-project-slug> \
 		http://localhost:3000 \
 		https://example.org
 
 Please note that you can not set a path in the `[publish-url]`!
 
+### Ports
+
 Per default, the proxy listens on port 4000. If you want to listen on another port, use the
 port flag:
 
@@ -62,15 +87,21 @@ If your public URL is available on a non-standard HTTP/HTTPS port, you can set t
 		http://localhost:3000 \
 		https://example.org:1234
 
+### Multiple Domains
+
 If this proxy runs on a subdomain, and you want Ory's cookies (e.g. the session cookie) to
 be available on all of your domain, you can use the following CLI flag to customize the cookie
-domain:
+domain. You will also need to allow your subdomains in the CORS headers:
 
 	$ ory proxy --project <your-project-slug> \
 		--cookie-domain example.org \
+		--allowed-cors-origins https://www.example.org \
+		--allowed-cors-origins https://api.example.org \
 		http://127.0.0.1:3000 \
 		https://ory.example.org
 
+### Redirects
+
 Per default all default redirects will go to to `[publish-url]`. You can change this behavior using
 the `--default-redirect-url` flag:
 
@@ -82,12 +113,14 @@ the `--default-redirect-url` flag:
 Now, all redirects happening e.g. after login will point to `/welcome` instead of `/` unless you
 have specified custom redirects in your Ory configuration or in the flow's `?return_to=` query parameter.
 
+### JSON Web Token
+
 If the request is not authenticated, the HTTP Authorization Header will be empty:
 
 	GET / HTTP/1.1
 	Host: localhost:3000
 
-If the request was authenticated, a JSON Web Token will be sent in the HTTP Authorization Header containing the
+If the request was authenticated, a JSON Web Token can be sent in the HTTP Authorization Header containing the
 Ory Session:
 
 	GET / HTTP/1.1
@@ -123,19 +156,33 @@ An example payload of the JSON Web Token is:
 
 
 ```
-ory proxy app-url [publish-url] [flags]
+ory proxy application-url [publish-url] [flags]
+```
+
+### Examples
+
+```
+ory proxy http://localhost:3000 --dev
+ory proxy http://localhost:3000 https://app.example.com \
+	--allowed-cors-origins https://www.example.org \
+	--allowed-cors-origins https://api.example.org \
+	--allowed-cors-origins https://www.another-app.com
+
 ```
 
 ### Options
 
 ```
-      --cookie-domain string          Set a dedicated cookie domain.
-      --default-redirect-url string   Set the URL to redirect to per default after e.g. login or account creation.
-  -h, --help                          help for proxy
-      --no-jwt                        Do not create a JWT from the Ory Kratos Session. Useful if you need fast start up times of the Ory Proxy.
-      --open                          Open the browser when the proxy starts.
-      --port int                      The port the proxy should listen on. (default 4000)
-      --project string                The slug of your Ory Cloud Project.
+      --allowed-cors-origins strings   A list of allowed CORS origins. Wildcards are allowed.
+      --cookie-domain string           Set a dedicated cookie domain.
+      --debug                          Use this flag to debug, for example, CORS requests.
+      --default-redirect-url string    Set the URL to redirect to per default after e.g. login or account creation.
+      --dev                            Use this flag when developing locally.
+  -h, --help                           help for proxy
+      --no-jwt                         Do not create a JWT from the Ory Kratos Session. Useful if you need fast start up times of the Ory Proxy.
+      --open                           Open the browser when the proxy starts.
+      --port int                       The port the proxy should listen on. (default 4000)
+      --project string                 The slug of your Ory Cloud Project.
 ```
 
 ### SEE ALSO

docs/cli/ory-tunnel.md

@@ -15,16 +15,15 @@ Tunnel Ory on a subdomain of your app or a separate port your app's domain
 
 ### Synopsis
 
-
 This command runs an HTTP Server which is connected to Ory's APIs, in order for your application and Ory's
 APIs to run on the same top level domain (for example yourapp.com, localhost). Having Ory on your domain
 is required for cookies to work.
 
 The first argument `application-url` points to the location of your application. This location
 will be used as the default redirect URL for the tunnel, for example after a successful login.
 
-    $ ory tunnel https://www.example.org --project <your-project-slug>
-    $ ory tunnel http://localhost:3000 --project <your-project-slug>
+    $ ory tunnel --project <your-project-slug> https://www.example.org
+    $ ORY_PROJECT_SLUG=<your-project-slug> ory tunnel http://localhost:3000
 
 ### Connecting to Ory