Raspberry Pi 3 - Browser Client - Revision history

Alpineuser: /* Related Links */

2025-12-31T05:51:47Z

Alpineuser: /* How do I backup firefox about:config edits? */

2025-07-23T09:37:09Z

How do I backup firefox about:config edits?

← Older revision		Revision as of 09:37, 23 July 2025
Line 239:		Line 239:
	===How do I backup firefox about:config edits?===		===How do I backup firefox about:config edits?===
	Use lbu include, and point to the 'full path' of the file. Finally, set it with lbu_commit -d. You can review the page for [[lbu]], for more details. A trap, is that if you use a relative path, it will also include a relative (useless) path in /etc/apk/protected_paths.d/lbu.list		Use lbu include, and point to the 'full path' of the file. Finally, set it with lbu_commit -d. You can review the page for [[lbu]], for more details. A trap, is that if you use a relative path, it will also include a relative (useless) path in /etc/apk/protected_paths.d/lbu.list
			===Ntpd configuration===
			The default ntp is busybox. You can run setup-ntp but that only chooses which daemon to run. If you want to change the default ntp command line options, you are looking for /etc/conf.d/. A mistake is to try to change the /etc/init.d/ntpd script. Both the script and the conf.d have pool.ntp.org set, but the conf.d file takes precedence.

	==Related Links==		==Related Links==

Alpineuser: /* Browser Client Install */

2025-07-08T14:24:11Z

Browser Client Install

← Older revision		Revision as of 14:24, 8 July 2025
Line 96:		Line 96:
	{{cmd\|# apk add xf86-video-fbdev}}		{{cmd\|# apk add xf86-video-fbdev}}

	<small>note: this command can vary if you are using x86. For example, I installed no xf86-video... drivers, and had a libEGL.so missing library error on Xorg that was resolved with "apk search libEGL.so" which pointed to mesa-egl. Note: apk search is case sensitive. Some other video drivers may be xf86-video-intel, xf86-video-vesa... Refer to the Xorg logs if you get an error with the display drivers.</small>		<small>note: this command can vary if you are using x86. For example, I installed no xf86-video... drivers, and had a libEGL.so missing library error on Xorg that was resolved with "apk search libEGL.so" which pointed to mesa-egl. Note: apk search is case sensitive. Some other video drivers may be xf86-video-intel, xf86-video-vesa... Refer to the Xorg logs if you get an error with the display drivers. This is pretty easy, as when X loaded for me, I could see in the logs that it was trying to look for a couple backends (intel, fbdev, vesa) and while installing one didn't work another did. However, you have to make sure to edit the xinitrc files otherwise, when it is working, it will run then close, if you didn't tell it start any program. the backends are viewable with apk search xf86-video of course.</small>

	At this point, we have about 421MB of RAM used (if NTP was not set up).		At this point, we have about 421MB of RAM used (if NTP was not set up).

Alpineuser: /* How do I easily backup my diskless system? */

2025-07-08T13:43:26Z

How do I easily backup my diskless system?

← Older revision		Revision as of 13:43, 8 July 2025
Line 236:		Line 236:
	===How do I easily backup my diskless system?===		===How do I easily backup my diskless system?===
	You should backup the apkvol which is located in /media/mmc (the location of the sd card).		You should backup the apkvol which is located in /media/mmc (the location of the sd card).

			===How do I backup firefox about:config edits?===
			Use lbu include, and point to the 'full path' of the file. Finally, set it with lbu_commit -d. You can review the page for [[lbu]], for more details. A trap, is that if you use a relative path, it will also include a relative (useless) path in /etc/apk/protected_paths.d/lbu.list

	==Related Links==		==Related Links==

Alpineuser at 08:52, 15 November 2024

2024-11-15T08:52:02Z

← Older revision		Revision as of 08:52, 15 November 2024
Line 2:		Line 2:

	This guide (more or less, I may have made some other customizations) Production tested with 3.13.5 (on RPI4) and stable for over 3 years. I have also run this on 3.17 with x86 (not tested as long).		This guide (more or less, I may have made some other customizations) Production tested with 3.13.5 (on RPI4) and stable for over 3 years. I have also run this on 3.17 with x86 (not tested as long).

			Note that this guide started out with an RPI3, has been used with x86, and currently runs with an RPI4, though the guide hasn't been fully updated yet. Hopefully, when time permits, and I have to remake the sign (or a new one) I will be able to edit this doc to represent either the RPI4 or RPI5 with alpine.

	==Overview==		==Overview==

Alpineuser at 08:50, 15 November 2024

2024-11-15T08:50:03Z

← Older revision		Revision as of 08:50, 15 November 2024
Line 1:		Line 1:
	This is a guide for setting up a RAM based Alpine which is able to run X, and firefox. This tutorial will go through setting up auto login, and starting X on boot without user interaction, useful as a kiosk or for digital signage.		This is a guide for setting up a RAM based Alpine which is able to run X, and firefox. This tutorial will go through setting up auto login, and starting X on boot without user interaction, useful as a kiosk or for digital signage. Later on I will use chromium which was used for a production sign and runs well, with a local website.

	This guide (more or less, I may have made some other customizations) Production tested with 3.13.5 (on RPI4) and stable for over 3 years. I have also run this on 3.17 with x86 (not tested as long).		This guide (more or less, I may have made some other customizations) Production tested with 3.13.5 (on RPI4) and stable for over 3 years. I have also run this on 3.17 with x86 (not tested as long).

Alpineuser at 08:49, 15 November 2024

2024-11-15T08:49:00Z

← Older revision		Revision as of 08:49, 15 November 2024
Line 1:		Line 1:
	This is a guide for setting up a RAM based Alpine which is able to run X, and firefox. This tutorial will go through setting up auto login, and starting X on boot without user interaction, useful as a kiosk or for digital signage.		This is a guide for setting up a RAM based Alpine which is able to run X, and firefox. This tutorial will go through setting up auto login, and starting X on boot without user interaction, useful as a kiosk or for digital signage.

	~~Current revision rough~~ tested with 3.17 (on x86)~~. For earlier releases, please see history~~.		This guide (more or less, I may have made some other customizations) Production tested with 3.13.5 (on RPI4) and stable for over 3 years. I have also run this on 3.17 with x86 (not tested as long).

	==Overview==		==Overview==
	This guide uses the following:		This guide uses the following:
	* aarch64 img (though this guide is also tested to be roughly x86-compatible)		* aarch64 img (though this guide is also tested to be roughly x86-compatible)
	* Raspberry Pi3		* Raspberry Pi3
	* community repo.		* community repo.

Line 231:		Line 231:
	===Firefox-esr segmentation fault on x86 for 3.17===		===Firefox-esr segmentation fault on x86 for 3.17===
	In running firefox on an old intel atom netbook, I see firefox having a 'segmentation fault' when trying to run. However dwm works. This may be due to the netbook being x86 (and atom). Chromium is x86-64 only in pkgs.alpinelinux.org so something to keep in mind when allocating for a given setup.		In running firefox on an old intel atom netbook, I see firefox having a 'segmentation fault' when trying to run. However dwm works. This may be due to the netbook being x86 (and atom). Chromium is x86-64 only in pkgs.alpinelinux.org so something to keep in mind when allocating for a given setup.

	===How do I easily backup my diskless system?===		===How do I easily backup my diskless system?===
	You should backup the apkvol which is located in /media/mmc (the location of the sd card).		You should backup the apkvol which is located in /media/mmc (the location of the sd card).

Alpineuser: /* Firefox-esr segmentation fault on x86 for 3.17 */

2024-11-15T08:36:33Z

Firefox-esr segmentation fault on x86 for 3.17

← Older revision		Revision as of 08:36, 15 November 2024
Line 231:		Line 231:
	===Firefox-esr segmentation fault on x86 for 3.17===		===Firefox-esr segmentation fault on x86 for 3.17===
	In running firefox on an old intel atom netbook, I see firefox having a 'segmentation fault' when trying to run. However dwm works. This may be due to the netbook being x86 (and atom). Chromium is x86-64 only in pkgs.alpinelinux.org so something to keep in mind when allocating for a given setup.		In running firefox on an old intel atom netbook, I see firefox having a 'segmentation fault' when trying to run. However dwm works. This may be due to the netbook being x86 (and atom). Chromium is x86-64 only in pkgs.alpinelinux.org so something to keep in mind when allocating for a given setup.
			===How do I easily backup my diskless system?===
			You should backup the apkvol which is located in /media/mmc (the location of the sd card).

	==Related Links==		==Related Links==

Zcrayfish: /* Disable Screensaver, and refresh webpage (optional) */ use pkg template. Remove the underscores from the red wikilink.

2024-01-10T14:25:52Z

Disable Screensaver, and refresh webpage (optional): use pkg template. Remove the underscores from the red wikilink.

← Older revision		Revision as of 14:25, 10 January 2024
Line 159:		Line 159:
	===Disable Screensaver, and refresh webpage (optional)===		===Disable Screensaver, and refresh webpage (optional)===

	As a kiosk, a Raspberry Pi needs to have the screensaver ([[~~Display_Power_Management_Signaling~~ DPMS]]) disabled.{{citation needed}} My particular application (video streams) required a refresh occasionally. These were managed with xorg.conf, xdotool, and crontab respectively.		As a kiosk, a Raspberry Pi needs to have the screensaver ([[Display Power Management Signaling DPMS]]) disabled.{{citation needed}} My particular application (video streams) required a refresh occasionally. These were managed with xorg.conf, xdotool, and crontab respectively.

	{{cat\|/etc/X11/xorg.conf\|		{{cat\|/etc/X11/xorg.conf\|
Line 166:		Line 166:
	EndSection}}		EndSection}}

	{{cmd\|# apk add xdotool}}		{{cmd\|# apk add {{pkg\|xdotool\|arch=a*}}}}

	<pre># crontab -u root -e		<pre># crontab -u root -e

Zcrayfish: /* Digital Signage */ Use pkg template.

2024-01-10T14:24:22Z

Digital Signage: Use pkg template.

← Older revision		Revision as of 14:24, 10 January 2024
Line 184:		Line 184:
	In this addition to the guide above, we'll install Chromium, which seems to be the defacto standard. However, you could use any X-Window application. Here we'll also run a web server with PHP, which hosts the resources we want to display on the sign.		In this addition to the guide above, we'll install Chromium, which seems to be the defacto standard. However, you could use any X-Window application. Here we'll also run a web server with PHP, which hosts the resources we want to display on the sign.
	Make sure community apk is enabled in {{path\|/etc/apk/repositories}}		Make sure community apk is enabled in {{path\|/etc/apk/repositories}}
	{{cmd\|# apk add chromium}}		{{cmd\|# apk add {{pkg\|chromium\|arch=a*}}}}
	In {{path\|/etc/startup.sh}} add chromium instead of firefox:		In {{path\|/etc/startup.sh}} add chromium instead of firefox:
	{{cat\|/etc/startup.sh\|<nowiki>...		{{cat\|/etc/startup.sh\|<nowiki>...

← Older revision		Revision as of 05:51, 31 December 2025
Line 246:		Line 246:
	* [[Raspberry Pi]]		* [[Raspberry Pi]]
	* [[Apache]]		* [[Apache]]
			* [https://lowendbox.com/blog/yes-you-can-run-18-static-sites-on-a-64mb-link-1-vps/ Low End Box - Yes, you can run 18 static sites on a 65mb link-1 vps] - A similar guide of removing programs to save on RAM use.


	[[Category:Raspberry]]		[[Category:Raspberry]]

← Older revision		Revision as of 14:24, 10 January 2024
Line 184:		Line 184:
	In this addition to the guide above, we'll install Chromium, which seems to be the defacto standard. However, you could use any X-Window application. Here we'll also run a web server with PHP, which hosts the resources we want to display on the sign.		In this addition to the guide above, we'll install Chromium, which seems to be the defacto standard. However, you could use any X-Window application. Here we'll also run a web server with PHP, which hosts the resources we want to display on the sign.
	Make sure community apk is enabled in {{path\|/etc/apk/repositories}}		Make sure community apk is enabled in {{path\|/etc/apk/repositories}}
	{{cmd\|# apk add chromium}}		{{cmd\|# apk add {{pkg\|chromium\|arch=a*}}}}
	In {{path\|/etc/startup.sh}} add chromium instead of firefox:		In {{path\|/etc/startup.sh}} add chromium instead of firefox:
	{{cat\|/etc/startup.sh\|<nowiki>...		{{cat\|/etc/startup.sh\|<nowiki>...