start-fullscreen mode vs kiosk mode

[nenonano]

Hi there

thank you for this very nice piece of code :-)
I have about 10 raspberrys which I'm moving from wayfile.ini approach to piosk
so far, so good.

the only issue I have is that I need --start-fullscreeen and --incognito flags for chromium instead of --kiosk; this is because raspies are without kb and mouse, and sometimes must be managed from vnc (peole not ssh/cli aware here).

I already modified runner.sh but I know that I'll loose my setup every time I'll update..
so, the final question: which is the best way to keep my modified runner.sh so it will survive an update?

TIA

[debloper]

Great to hear that you've been using PiOSK, moving from the the tedious wayfire.ini tutorial.

I'm unclear what's the issue with connecting to Pi over VNC while it's running Chromium in --kiosk mode. If you could provide some context (or even a link to read up), that'd be appreciated.

I can think of ways to parameterize the chromium flags as "advanced" features in the management dashboard, but the effort vs utility makes it hard to prioritize.

I'm open to evaluate the idea; but need more context of the actual issue being faced.

[nenonano]

Hi, thank you for your fast response.
having chromium in kiosk mode is a problem for who is in charge to maintain the raspberries.. they cannot escape from chromium and the full-screen way is easier.. they just have to press F11 to gain access to the desktop..
I think that using parameters for chromium would be a great idea

[debloper]

Seems like a very esoteric usecase that's doesn't quite align with the conventions of a device in Kiosk mode. Unfortunately, I don't think we can provide a built-in support for these kinda configurations management; but really glad that you've found a way out that works for you.