mgr/dashboard: Use HTTPS in dev proxy configuration

- After SSL support has been added to Ceph Dashboard via PR #21627, the developer HTTP proxy sample config must be adapted.
- Adapt HACKING.rst to use HTTPS.

Signed-off-by: Volker Theile <vtheile@suse.com>

diff --git a/src/pybind/mgr/dashboard/HACKING.rst b/src/pybind/mgr/dashboard/HACKING.rst
index a5084f2dd2e06f00504181d1aa4913e90693275f..d3c579f4f08dc3f540174b3ce64f444993e5a608 100644 (file)
--- a/src/pybind/mgr/dashboard/HACKING.rst
+++ b/src/pybind/mgr/dashboard/HACKING.rst
@@ -61,7 +61,7 @@ Build the Project
 
 Run ``npm run build`` to build the project. The build artifacts will be
 stored in the ``dist/`` directory. Use the ``-prod`` flag for a
-production build. Navigate to ``http://localhost:8080``.
+production build. Navigate to ``https://localhost:8080``.
 
 Running Unit Tests
 ~~~~~~~~~~~~~~~~~~
@@ -265,11 +265,11 @@ following code::
 Every path given in the ``ApiController`` decorator will automatically be
 prefixed with ``api``. After reloading the Dashboard module you can access the
 above mentioned controller by pointing your browser to
-http://mgr_hostname:8080/api/ping2.
+https://mgr_hostname:8080/api/ping2.
 
 It is also possible to have nested controllers. The ``RgwController`` uses
 this technique to make the daemons available through the URL
-http://mgr_hostname:8080/api/rgw/daemon::
+https://mgr_hostname:8080/api/rgw/daemon::
 
   @ApiController('rgw')
   @AuthRequired()

diff --git a/src/pybind/mgr/dashboard/frontend/proxy.conf.json.sample b/src/pybind/mgr/dashboard/frontend/proxy.conf.json.sample
index e654419c9cfd588079041120542f73b4f95a40e1..d70abbd2c93e40516151d0df27a384ef0ac9a5c3 100644 (file)
--- a/src/pybind/mgr/dashboard/frontend/proxy.conf.json.sample
+++ b/src/pybind/mgr/dashboard/frontend/proxy.conf.json.sample
@@ -1,6 +1,6 @@
 {
   "/api/": {
-    "target": "http://localhost:8080",
+    "target": "https://localhost:8080",
     "secure": false,
     "logLevel": "debug"
   }