Merge pull request #42 from tucksaun/wildcard-routes-doc-improvement

fabpot · web-flow · commit f862e097a729 · 2019-11-14T10:17:00.000+01:00
Be more precise in wildcard routes documentation
diff --git a/cookbooks/go_live.rst b/cookbooks/go_live.rst
@@ -78,8 +78,9 @@ layer to route requests to the project for a specific domain:
 
 .. tip::
 
-    Multiple domains can be attached to a project. Wildcard domains (like
-    ``*.example.com``) are also supported.
+    Multiple domains can be attached to a project. :ref:`wildcard_routes` (like
+    ``*.example.com``) are also supported using the ``.symfony/routes.yaml``
+    file.
 
 If you require access to the project before the domain name switch is done, you
 can create a ``hosts`` file entry on your computer and point it directly to one
diff --git a/routes.rst b/routes.rst
@@ -101,6 +101,8 @@ different applications:
         # "blog" is the name defined in another .symfony.cloud.yaml
         upstream: "blog:http"
 
+.. _wildcard_routes:
+
 Wildcard Routes
 ~~~~~~~~~~~~~~~
 
@@ -110,7 +112,18 @@ as any other routes; routed to an application or redirected to another one.
 To create a wildcard route, prefix the route with a star (``*``). For example
 ``*.example.com`` matches any HTTP requests to ``www.example.com``,
 ``blog.example.com``, or ``us.example.com`` once the wildcard domain
-(``*.example.com``) is added to the project.
+(``*.example.com``) is added to the project:
+
+.. code-block:: yaml
+
+    "https://{all}/":
+        type: upstream
+        upstream: "app:http"
+
+    "https://*.{default}/":
+        type: upstream
+        upstream: "app:http"
+
 
 .. caution::
 
