feat: clarify port forward documentation (#510)

Qovery · Jan 17, 2025 · f6177f1 · f6177f1
1 parent 2f7b827
commit f6177f1
Show file tree

Hide file tree

Showing 2 changed files with 17 additions and 3 deletions.
diff --git a/website/docs/using-qovery/interface/cli.md b/website/docs/using-qovery/interface/cli.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2025-01-02"
+last_modified_on: "2025-01-17"
 title: CLI
 description: How to use the Qovery CLI (Command Line Interface)
 ---
@@ -478,8 +478,15 @@ Please type "yes" to validate context: yes
 Listening on 127.0.0.1:8000 => 80
 ```
 
-The port-forward feature works with any `application`, `Cronjob`, `Lifecycle job` or `database` (Container or Managed) deployed with Qovery. For `Managed database` instances on AWS, once the port-forwarded is activated, you must specify ~ `--tls` and `--tls-insecure` in your database connection command since localhost is not the valid hostname.
+The port-forward feature works with any `application`, `Cronjob`, `Lifecycle job` or `database` (Container or Managed) deployed with Qovery.
 
+Im this example, you can now connect on `http://localhost:8000` to access your application.
+
+<Alert type="info">
+
+For `Managed database` instances on AWS, once the port-forwarded is activated, you must specify ~ `--tls` and `--tls-insecure` **in your database connection** command since localhost is not the valid hostname.
+
+</Alert>
 
 ### Port-forward a dedicated pod
 

diff --git a/website/docs/using-qovery/interface/cli.md.erb b/website/docs/using-qovery/interface/cli.md.erb
@@ -313,8 +313,15 @@ Please type "yes" to validate context: yes
 Listening on 127.0.0.1:8000 => 80
 ```
 
-The port-forward feature works with any `application`, `Cronjob`, `Lifecycle job` or `database` (Container or Managed) deployed with Qovery. For `Managed database` instances on AWS, once the port-forwarded is activated, you must specify ~ `--tls` and `--tls-insecure` in your database connection command since localhost is not the valid hostname.
+The port-forward feature works with any `application`, `Cronjob`, `Lifecycle job` or `database` (Container or Managed) deployed with Qovery.
 
+Im this example, you can now connect on `http://localhost:8000` to access your application.
+
+<Alert type="info">
+
+For `Managed database` instances on AWS, once the port-forwarded is activated, you must specify ~ `--tls` and `--tls-insecure` **in your database connection** command since localhost is not the valid hostname.
+
+</Alert>
 
 ### Port-forward a dedicated pod