Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Config #61

Open
helmi1987 opened this issue Feb 14, 2020 · 1 comment
Open

Default Config #61

helmi1987 opened this issue Feb 14, 2020 · 1 comment

Comments

@helmi1987
Copy link

Hallo

is it possible to set a default config over a script?

i mean when i will install the extension on 10 Clients with the same setting is this possible without configure this on all client manually.

@maglub
Copy link

maglub commented Apr 3, 2020

This might be tricky, due to the security mechanism of Chrome and Chromium. What we are fighting here is that the browser is very restrictive about what it allow you to do, concerning plugins which might be malware.

I do this in a crude way, so that I can fleet manage Chromium based signage screens, running Raspbian Lite on Raspberry Pi 4:

  • I start chromium on screen 1:
chromeConfigDir=screen1
/usr/bin/chromium-browser --user-data-dir=/home/dashboard/.config/'${chromeConfigDir}' --password-store=basic"
  • I install the plugins that I need (i.e TabRotate)
  • Set up TabRotate to look for a local json file, i.e /home/dashboard/dashboard-config.json.
  • Set TabRotate to start in full screen mode
  • Exit Chromium, and save that config to a tar-file to use as a template when I install a new system
cd .config
tar cvzf screen1.tar screen1

When installing a new computer I automatically install a i3 and lightdm, set up a new user, then unpack that config into the ~/.config directory of that user and starts Chromium the same way as described above, pointing out that configuration.

Whenever I need to show a new set of web pages, I just need to create a new /home/dashboard/dashboard-config.json file, and TabRotate will see that it has changed and update the screen accordingly.

If you have multiple screens, you just do it again, with different parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants