From 8dfb6223f97f435fd5c6145650374e6b8e119ce5 Mon Sep 17 00:00:00 2001 From: Josef Reidinger Date: Mon, 8 Apr 2024 13:38:09 +0200 Subject: [PATCH 1/2] adapt debugging hints --- web/README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/web/README.md b/web/README.md index 746d1012e6..31eb0e98a3 100644 --- a/web/README.md +++ b/web/README.md @@ -27,7 +27,7 @@ This can work also remotely, with a Agama instance running in a different machine (a virtual machine as well). In that case run ``` - AGAMA_SERVER= npm run server -- --open + AGAMA_SERVER=https://: npm run server -- --open ``` Where `AGAMA_SERVER` is the IP address, the hostname or the full URL of the @@ -40,11 +40,12 @@ Example of running from different machine: ``` # backend machine # using ip of machine instead of localhost is important to be network accessible - agama-web-server serve --address 10.100.1.1:3000 + # second address is needed for SSL which is mandatory for remote access + agama-web-server serve --address 10.100.1.1:3000 --address2 0.0.0.0:443 # frontend machine # ESLINT=0 is useful to ignore linter problems during development - ESLINT=0 AGAMA_SERVER=10.100.1.1:3000 npm run server + ESLINT=0 AGAMA_SERVER=https://10.100.1.1:3000 npm run server ``` ### Debugging Hints @@ -54,6 +55,8 @@ The first place is the browser's console which can give some hints. The second location to check for errors or warnings is output of `npm run server` where you can find issues when communicating with the backend. And last but on least is journal on backend machine where is logged backend activity `journalctl -b`. +If journal does not provide required info, there is also option to see dbus communication +which can give hint about data flow. Command is `busctl monitor --address /run/agama/bus` ### Special Environment Variables From 3123d1c7b294278c5c88a922d8a7d4739bca6d02 Mon Sep 17 00:00:00 2001 From: Josef Reidinger Date: Mon, 8 Apr 2024 14:22:54 +0200 Subject: [PATCH 2/2] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Ladislav Slezák Co-authored-by: Imobach González Sosa --- web/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/web/README.md b/web/README.md index 31eb0e98a3..24f3db9d1c 100644 --- a/web/README.md +++ b/web/README.md @@ -41,7 +41,7 @@ Example of running from different machine: # backend machine # using ip of machine instead of localhost is important to be network accessible # second address is needed for SSL which is mandatory for remote access - agama-web-server serve --address 10.100.1.1:3000 --address2 0.0.0.0:443 + agama-web-server serve --address :::3000 --address2 :::443 # frontend machine # ESLINT=0 is useful to ignore linter problems during development @@ -55,8 +55,8 @@ The first place is the browser's console which can give some hints. The second location to check for errors or warnings is output of `npm run server` where you can find issues when communicating with the backend. And last but on least is journal on backend machine where is logged backend activity `journalctl -b`. -If journal does not provide required info, there is also option to see dbus communication -which can give hint about data flow. Command is `busctl monitor --address /run/agama/bus` +If the journal does not contain the required info, you can inspect the D-Bus communication +which can give hint about data flow. Command is `busctl monitor --address unix:path=/run/agama/bus` ### Special Environment Variables