PIXILAB Wiki

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
blocks:porteus_kiosk_dev [2023-11-15 12:45]
mattias [Using SSH] 		blocks:porteus_kiosk_dev [2024-03-13 07:57] (current)
mattias [Using SSH]
Line 14: Line 14:
 dhcp=yes dhcp=yes
 browser=chrome browser=chrome
-homepage_append=mac 
 homepage=http://pixi.guide/spot homepage=http://pixi.guide/spot
 disable_private_mode=yes disable_private_mode=yes
-homepage_check=PIXLAB Blocks Server can't be reached. Please check your network connections. 
 wake_on_lan=yes wake_on_lan=yes
 disable_zoom_controls=yes disable_zoom_controls=yes
Line 24: Line 22:
 additional_components=uefi.zip initrdpxe.xz 08-ssh.xzm additional_components=uefi.zip initrdpxe.xz 08-ssh.xzm
 root_password=pixi root_password=pixi
-browser_preferences=http://pixi.guide/public/chrome-policies.txt 
 hide_mouse=no hide_mouse=no
 disable_navigation_bar=no disable_navigation_bar=no
Line 35: Line 32:
   * Show the mouse   * Show the mouse
   * Show the navigation bar   * Show the navigation bar
-  * Enable  a chrome policy file stored on the Blocks server, with this any chrome policies can be set on the kiosks to change browser polices. 
  
  
-==== 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 ==== ==== Using SSH ====
Line 63: Line 44:
  
 :!: On Windows, you must enable //OpenSSH Client// under "Windows optional features". :!: On Windows, you must enable //OpenSSH Client// under "Windows optional features".
 +
  
 <code> <code>
Line 76: Line 58:
   - Use the ssh command again, as shown above, to access the player   - 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 editor or in the dhcp servers client lease list.