From f6177f10c6ef347bdcb54db02f2ed9f23445aa59 Mon Sep 17 00:00:00 2001 From: Pierre Mavro Date: Fri, 17 Jan 2025 11:38:42 +0100 Subject: [PATCH] feat: clarify port forward documentation (#510) --- website/docs/using-qovery/interface/cli.md | 11 +++++++++-- website/docs/using-qovery/interface/cli.md.erb | 9 ++++++++- 2 files changed, 17 insertions(+), 3 deletions(-) diff --git a/website/docs/using-qovery/interface/cli.md b/website/docs/using-qovery/interface/cli.md index dc74326a87..4f57ddc467 100644 --- 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. + + + +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. + + ### 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 index f78d03558e..6638ec9945 100644 --- 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. + + + +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. + + ### Port-forward a dedicated pod