|
11 | 11 | # run on the same proxy. |
12 | 12 | # |
13 | 13 | proxy: |
| 14 | + |
14 | 15 | # Hosts |
15 | 16 | # |
16 | 17 | # The hosts that will be used to serve the app. The proxy will only route requests |
|
48 | 49 |
|
49 | 50 | # Custom SSL certificate |
50 | 51 | # |
51 | | - # In some cases, using Let's Encrypt for automatic certificate management is not an |
52 | | - # option, or you may already have SSL certificates issued by a different |
53 | | - # Certificate Authority (CA). Kamal supports loading custom SSL certificates |
| 52 | + # In some cases, using Let's Encrypt for automatic certificate management is not an |
| 53 | + # option, or you may already have SSL certificates issued by a different |
| 54 | + # Certificate Authority (CA). Kamal supports loading custom SSL certificates |
54 | 55 | # directly from secrets. |
55 | 56 | # |
56 | 57 | # Examples: |
@@ -84,12 +85,12 @@ proxy: |
84 | 85 |
|
85 | 86 | # Path-based routing |
86 | 87 | # |
87 | | - # For applications that split their traffic to different services based on the request path, |
| 88 | + # For applications that split their traffic to different services based on the request path, |
88 | 89 | # you can use path-based routing to mount services under different path prefixes. |
89 | 90 | path_prefix: '/api' |
90 | | - # By default, the path prefix will be stripped from the request before it is forwarded upstream. |
91 | | - # So in the example above, a request to /api/users/123 will be forwarded to web-1 as /users/123. |
92 | | - # To instead forward the request with the original path (including the prefix), |
| 91 | + # By default, the path prefix will be stripped from the request before it is forwarded upstream. |
| 92 | + # So in the example above, a request to /api/users/123 will be forwarded to web-1 as /users/123. |
| 93 | + # To instead forward the request with the original path (including the prefix), |
93 | 94 | # specify --strip-path-prefix=false |
94 | 95 | strip_path_prefix: false |
95 | 96 |
|
|
0 commit comments