diff --git a/deploy-apps/routes-domains.html.md.erb b/deploy-apps/routes-domains.html.md.erb index 6c58ce8e..a8072311 100644 --- a/deploy-apps/routes-domains.html.md.erb +++ b/deploy-apps/routes-domains.html.md.erb @@ -277,6 +277,29 @@ Developers can only see routes in spaces where they are members.

Note: cf CLI v7 removes the port and path columns from the output.

+### View a Route + +Developers can view a route, and its destinations, within the current space with the cf route command. A route is uniquely identified by the combination of hostname, domain, port, and path. + +
+$ cf route <%= vars.app_domain %> --hostname myapp
+Showing route myapp.<%= vars.app_domain %> in org o / space my-space as admin...
+
+domain:     <%= vars.app_domain %>
+host:       myapp
+port:
+path:
+protocol:   http
+
+Destinations:
+        app      process   port   protocol
+        mystore  web       8080   http1
+
+ +Developers can only view a route when it's within a space where they are a member. + +

Note: this is only available in cf CLI v8.

+ ### Check Routes Developers cannot create a route that is already taken. To check whether a route is available, developers can use the [cf check-route](https://cli.cloudfoundry.org/en-US/cf/check-route.html) command. @@ -351,6 +374,12 @@ The following command maps the wildcard route `*.foo.<%= vars.app_domain %>` to $ cf map-route myfallbackapp foo.<%= vars.app_domain %> --hostname '*' +As of cf CLI v8, the following command maps the route `h2app.<%= vars.app_domain %>` as an HTTP/2 route to the HTTP/2 app `h2app`. + +
+$ cf map-route h2app <%= vars.app_domain %> --hostname h2app --destination-protocol http2
+
+ #### Map a Route with App Push Developers can map a route to their app with the `cf push` command.