Differences

This shows you the differences between two versions of the page.

--- blocks:porteus_kiosk_dev [2024-03-13 07:53]
mattias [PIXILAB Player with developer tools]
+++ blocks:porteus_kiosk_dev [2024-03-13 07:57]
mattias [Using SSH]
@@ Line 35: / Line 35: @@
-==== Managing PIXILAB Player Policies from your Blocks Server ====
-In some cases, when using the Chrome browser with PIXILAB Player, you may need to override the browser's policies. This can be done by storing a text file named chrome-policies.txt in the directory <your-blocks-root>/public/PIXILAB_Player (where "<your-block-root>" is the location of your Blocks root directory).The path to this file is then be specified in the kiosk-config.txt file used when creating the player the, as described above. This example assumes the default domain name //pixi.guide// (which in your case may be another domain name, or a hardcoded IP address).
-<code>browser_preferences=http://pixi.guide/public/PIXILAB_Player/chrome-policies.txt</code>
-The "chrome-policies.txt" file must contain the following policy to be able to access the Developer tools in Chrome.
-<code>
-"DeveloperToolsAvailability": 1,
-</code>
-More information on Chrome policies and syntax can be found [[https://www.chromium.org/administrators/policy-list-3|here]].
 ==== Using SSH ====
@@ Line 60: / Line 44: @@
 :!: On Windows, you must enable //OpenSSH Client// under "Windows optional features".
 <code>
@@ Line 73: / Line 58: @@
   - Use the ssh command again, as shown above, to access the player
+ To avoid the known host issue one can use:
+<code>
+$ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@[ip-number]
+</code>
+Ip number can be found in blocks or in the dhcp servers client lease list.