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 [2020-11-17 07:30]
mattias 		blocks:porteus_kiosk_dev [2024-03-13 07:57] (current)
mattias [Using SSH]
Line 1: Line 1:
 ====== PIXILAB Player with developer tools====== ====== PIXILAB Player with developer tools======
  
-Sometimes it is useful to create a kiosk with settings that enables some tools for trouble-shooting. +Sometimes it is useful to create a player with settings that enables some tools for trouble-shooting. 
-SSH access to the kiosk, toolbars and developer tools  can come in handy while testing scripts and hardware.  +SSH access to the player, toolbars and developer tools  can come in handy while testing scripts and hardware.  
  
 Follow the [[blocks:porteus_kiosk|guide to build a standard kiosk]] but use the settings provided here. Follow the [[blocks:porteus_kiosk|guide to build a standard kiosk]] but use the settings provided here.
  
-=== Kiosk Configuration file ===+=== Configuration File ===
  
-Use the text file method to configer the kiosk, edit and copy the text shown below to another FAT32-formatted USB stick. Put it at the root level of the USB stick, naming it //kiosk-config-dev.txt// or any other describing name. +Use the text file method to configure the player, edit and copy the text shown below to another FAT32-formatted USB stick. Put it at the root level of the USB stick, naming it //kiosk-config-dev.txt// or any other describing name. 
  
 <code> <code>
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. 
  
  
-==== Manage Pixilab Player Chrome Policies from the 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. +==== Using SSH ====
  
-<code>+In case you need to access the player with SSH, you first have to find its IP number. This can be found in the Blocks editor under Display spot settings/Information
  
-"DeveloperToolsAvailability": 1,+To log on, use a ssh enabled terminal window. 
  
 +:!: On Windows, you must enable //OpenSSH Client// under "Windows optional features".
  
-</code> 
- 
- 
-More information on Chrome policies and syntax can be found [[https://www.chromium.org/administrators/policy-list-3|here]].  
- 
-==== Use SSH ==== 
- 
-To log on to the kiosk with SSH one has to find out its current IP number. One method is to use the dhcps servers client leases list and look for the particular MAC adress.  
- 
-To log on, use a ssh enabled terminal. I´m on windows so I have enabled the OpenSSH Client in the Windows optional features. 
  
 <code> <code>
 $ ssh root@[ipnumber] $ ssh root@[ipnumber]
 </code> </code>
-Enter your password choosen in the kiosk-config file.+Enter the password specified in the kiosk-config file.
  
-On Windows, as a side effect from not storing anything persistent on the kiosk one has to reset the //known_hosts// file between eash connection. That is because the hash identifiying the Kiosk keeps changing. Simply open the //known_hosts// file  stored under your user in a hidden folder called //.ssh//  with atom or simular text editor and delete the entry with your kiosks IP number. Dont forget to save the file. Is is possible to do broader wildcard setting in the known_hosts file but I prefere this method. +On your computer used to access the player over SSH, you may have to reset the //known_hosts// file. That is because the hash identifying the player changes on each restart. To do so:
  
 +  - Open the //known_hosts// file  stored under your user in a hidden folder called //.ssh//  using a  [[blocks:drivers:tools|code editor]] or other plain text editor, such as Notepad.
 +  - Delete the line with your player's IP address. 
 +  - Save the file.
 +  - 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.