Top Related Projects
Lightweight justice for your single-board computer!
Scripts to build OctoPi, a Raspberry PI distro for controlling 3D printers over the web
A black hole for Internet advertisements
:beginner: Home Assistant Operating System
Quick Overview
FullPageOS is a Raspberry Pi operating system distribution designed to display a full-screen web browser on boot. It's based on the Raspberry Pi OS and includes features like automatic updates, remote management, and hardware-accelerated video playback. FullPageOS is ideal for digital signage, information kiosks, and other applications requiring a dedicated web-based display.
Pros
- Easy setup and configuration for full-screen web browsing
- Automatic updates and remote management capabilities
- Hardware-accelerated video playback for smooth performance
- Customizable with various plugins and add-ons
Cons
- Limited to web-based applications and content
- May require additional configuration for complex setups
- Potential security risks if not properly secured
- Dependent on stable internet connection for web-based content
Getting Started
To get started with FullPageOS:
- Download the latest FullPageOS image from the official GitHub repository.
- Flash the image to a microSD card using a tool like Etcher or Raspberry Pi Imager.
- Insert the microSD card into your Raspberry Pi and power it on.
- Connect to your Wi-Fi network or use an Ethernet cable for internet access.
- The system will boot directly into a full-screen web browser displaying the default webpage.
To customize the displayed webpage:
- SSH into your Raspberry Pi or use a keyboard connected directly to the device.
- Edit the configuration file located at
/boot/fullpageos.txt
. - Modify the
FULLPAGE_URL
variable to your desired webpage URL. - Save the file and reboot the Raspberry Pi.
For more advanced configuration options and customization, refer to the official documentation on the FullPageOS GitHub repository.
Competitor Comparisons
Lightweight justice for your single-board computer!
Pros of DietPi
- More versatile and supports a wider range of single-board computers and x86_64 devices
- Offers a broader selection of software options and configurations
- Actively maintained with frequent updates and a larger community
Cons of DietPi
- Requires more setup and configuration for kiosk-like functionality
- May have a steeper learning curve for users seeking a simple full-screen browser solution
Code Comparison
FullPageOS (config.txt snippet):
disable_overscan=1
overscan_left=0
overscan_right=0
overscan_top=0
overscan_bottom=0
DietPi (dietpi.txt snippet):
AUTO_SETUP_AUTOMATED=1
AUTO_SETUP_GLOBAL_PASSWORD=dietpi
AUTO_SETUP_KEYBOARD_LAYOUT=us
AUTO_SETUP_TIMEZONE=Europe/London
AUTO_SETUP_NET_ETHERNET_ENABLED=1
FullPageOS focuses on display settings for full-screen browsing, while DietPi's configuration file allows for broader system setup options.
Summary
FullPageOS is tailored for kiosk-style applications with minimal setup, ideal for users needing a quick full-screen browser solution. DietPi offers more flexibility and software choices but requires additional configuration for similar functionality. DietPi's active development and broader device support make it suitable for various projects beyond kiosk applications.
Scripts to build OctoPi, a Raspberry PI distro for controlling 3D printers over the web
Pros of OctoPi
- Specifically designed for 3D printing, offering a comprehensive solution for printer control and monitoring
- Includes OctoPrint, a powerful web interface for managing 3D printers
- Supports a wide range of 3D printer models and accessories
Cons of OctoPi
- Limited to 3D printing applications, less versatile for general-purpose use
- May require more setup and configuration for non-3D printing tasks
- Potentially higher resource usage due to specialized features
Code Comparison
OctoPi:
# Example OctoPrint plugin initialization
def __init__(self):
self.printer = None
self.printer_profile = None
self.temperature = None
FullPageOS:
# Example Chromium kiosk mode configuration
chromium_args = [
'--kiosk',
'--disable-pinch',
'--overscroll-history-navigation=0'
]
FullPageOS is more focused on creating a full-screen browser environment, while OctoPi is tailored for 3D printer management. The code snippets reflect their different purposes, with OctoPi initializing printer-related variables and FullPageOS configuring Chromium for kiosk mode.
A black hole for Internet advertisements
Pros of Pi-hole
- Focuses on network-wide ad blocking and privacy protection
- Extensive community support and regular updates
- Provides detailed statistics and monitoring capabilities
Cons of Pi-hole
- Limited to DNS-based blocking, may not block all ads
- Requires more technical knowledge to set up and maintain
- Not designed for full-screen web browsing or kiosk applications
Code Comparison
FullPageOS (Python):
def get_config():
config = ConfigParser.ConfigParser()
config.read(['/boot/fullpageos.txt', '/boot/fullpageos-network.txt'])
return config
Pi-hole (Bash):
setupVars="/etc/pihole/setupVars.conf"
if [[ -f "${setupVars}" ]]; then
source "${setupVars}"
fi
FullPageOS is primarily focused on creating a full-screen web browser experience for Raspberry Pi, while Pi-hole is designed as a network-wide ad blocker and DNS sinkhole. FullPageOS is more suitable for kiosk-style applications, whereas Pi-hole excels in improving network privacy and reducing unwanted content across all devices on a network.
:beginner: Home Assistant Operating System
Pros of Home Assistant Operating System
- More comprehensive smart home ecosystem with extensive device integrations
- Regular updates and active development from a large community
- Robust security features and containerized architecture
Cons of Home Assistant Operating System
- Steeper learning curve for beginners
- Requires more system resources compared to FullPageOS
- Less focused on single-purpose kiosk functionality
Code Comparison
FullPageOS (config.txt):
# Enable GPU memory
gpu_mem=128
# Enable audio
dtparam=audio=on
Home Assistant Operating System (cmdline.txt):
console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 fsck.repair=yes rootwait zram.enabled=1 zram.num_devices=1
Summary
FullPageOS is designed specifically for creating fullscreen kiosk displays, while Home Assistant Operating System offers a comprehensive smart home platform. FullPageOS is simpler to set up for single-purpose use, whereas Home Assistant OS provides more extensive features but requires more setup and resources. The code comparison shows that FullPageOS focuses on display-related configurations, while Home Assistant OS emphasizes system-level settings for its broader functionality.
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
FullPageOS
.. image:: https://github.com/guysoft/FullPageOS/blob/secularstevelogo/media/FullPageOS.png?raw=true .. :scale: 50 % .. :alt: FullPageOS logo
A Raspberry Pi <http://www.raspberrypi.org/>
_ distribution to display one webpage in full screen. It includes Chromium <https://www.chromium.org/>
_ out of the box and the scripts necessary to load it at boot.
This repository contains the source script to generate the distribution out of an existing Raspbian <http://www.raspbian.org/>
_ distro image.
FullPageOS started as a fork from OctoPi <https://github.com/guysoft/OctoPi>
, but then joined the distros that use CustomPiOS <https://github.com/guysoft/CustomPiOS>
.
Donate
FullPageOS is 100% free and open source and maintained by Guy Sheffer. If it's helping your life, your organisation or makes you happy, please consider making a donation. It means I can code more and worry less about my balance. Any amount counts.
|paypal|
.. |paypal| image:: https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif :target: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=26VJ9MSBH3V3W&source=url
Where to get it?
The official mirror is here <http://unofficialpi.org/Distros/FullPageOS/>
_
Nightly builds are available here <http://unofficialpi.org/Distros/FullPageOS/nightly/>
_ (currently built on demand)
How to use it?
#. Unzip the image and install it to an SD card like any other Raspberry Pi image <https://www.raspberrypi.org/documentation/installation/installing-images/README.md>
_
#. Configure your WiFi by editing wifi.nmconnection
on the first partition of the flashed card when using it like a flash drive
#. Boot the Pi from the SD card
#. Log into your Pi via SSH (it is located at fullpageos.local
if your computer supports bonjour <https://learn.adafruit.com/bonjour-zeroconf-networking-for-windows-and-linux/overview>
_ or the IP address assigned by your router), default username is "pi", default password is "raspberry" and change the password using the passwd
command. Consider also changing the vnc password as well by x11vnc -storepasswd
.
Requirements
- Raspberry Pi 2 and newer or device running Armbian. Older Raspberry Pis are not currently supported. See
Raspberry Pi <https://github.com/guysoft/FullPageOS/issues/12>
_ andRaspberry Pi <https://github.com/guysoft/FullPageOS/issues/43>
_. - SD card, 4GB or larger, Class 10. (Early June 2020 was the image size 3GB.)
- 2A power supply
Features
- Loads Chromium at boot in full screen
- Webpage can be changed from /boot/firmware/fullpageos.txt
- You can use variable
{serial}
in the url to get device's serialnumber in the URL
- You can use variable
- Default app is
FullPageDashboard <https://github.com/amitdar/FullPageDashboard>
_, which lets you add multiple tabs changes that switch automatically. - Ships with preconfigured
X11VNC <http://www.karlrunge.com/x11vnc/>
_, for remote connection (password 'raspberry') - Specify a custom Splashscreen that gets displayed in the booting process instead of Kernel messages/text
Developing
Requirements
#. `qemu-arm-static <http://packages.debian.org/sid/qemu-user-static>`_
#. `CustomPiOS <https://github.com/guysoft/CustomPiOS>`_
#. Downloaded `Raspbian <http://www.raspbian.org/>`_ image.
#. root privileges for chroot
#. Bash
#. realpath
#. sudo (the script itself calls it, running as root without sudo won't work)
#. jq (part of CustomPiOS dependencies)
Build FullPageOS From within FullPageOS / Raspbian / Debian / Ubuntu
FullPageOS can be built from Debian, Ubuntu, Raspbian, or even FullPageOS. Build requires about 2.5 GB of free space available. You can build it by issuing the following commands::
sudo apt install coreutils p7zip-full qemu-user-static
git clone https://github.com/guysoft/CustomPiOS.git
git clone https://github.com/guysoft/FullPageOS.git
cd FullPageOS/src/image
wget -c --trust-server-names 'https://downloads.raspberrypi.org/raspios_lite_armhf_latest'
cd ..
../../CustomPiOS/src/update-custompios-paths
sudo modprobe loop
sudo bash -x ./build_dist
Building FullPageOS Variants
FullPageOS supports building variants, which are builds with changes from the main release build. An example and other variants are available in the folder ``src/variants/example``.
To build a variant use::
sudo bash -x ./build_dist [Variant]
Building Using Docker
~~~~~~~~~~~~~~~~~~~~~~
`See Building with docker entry in wiki <https://github.com/guysoft/CustomPiOS/wiki/Building-with-Docker>`_
Building Using Vagrant
~~~~~~~~~~~~~~~~~~~~~~
There is a vagrant machine configuration to let build FullPageOS in case your build environment behaves differently. Unless you do extra configuration, vagrant must run as root to have nfs folder sync working.
Make sure you have a version of vagrant later than 1.9!
If you are using older versions of Ubuntu/Debian and not using apt-get `from the download page <https://www.vagrantup.com/downloads.html>`_.
To use it::
sudo apt-get install vagrant nfs-kernel-server virtualbox
sudo vagrant plugin install vagrant-nfs_guest
sudo modprobe nfs
cd FullPageOS/src/vagrant
sudo vagrant up
After provisioning the machine, it's also possible to run a nightly build which updates from devel using::
cd FullPageOS/src/vagrant
run_vagrant_build.sh
To build a variant on the machine simply run::
cd FullPageOS/src/vagrant
run_vagrant_build.sh [Variant]
Usage
~~~~~
#. If needed, override existing config settings by creating a new file ``src/config.local``. You can override all settings found in ``src/config``. If you need to override the path to the Raspbian image to use for building OctoPi, override the path to be used in ``ZIP_IMG``. By default, the most recent file matching ``*-raspbian.zip`` found in ``src/image`` will be used.
#. Run ``src/build_dist`` as root.
#. The final image will be created in ``src/workspace``
Remote access
~~~~~~~~~~~~~
Remote GUI access can be achieved through VNC Viewer. Get the IP of your raspberry ``hostname -I`` via SSH.
The password is ``raspberry`` and is independent of password you have set for your user(s). Change the password by ``x11vnc -storepasswd`` via SSH.
Install Chrome Extensions
Press ctrl
+ t
, it will open a new tab.
You can either install extensions from Chrome Web Store <https://chrome.google.com/webstore/category/extensions>
_ or install your own extension <https://support.google.com/chrome_webstore/answer/2664769?hl=en>
_.
If you wish to install your own extension then you can transfer the build files via tools like rcp
, rsync
etc.
Example::
rsync -av <extension-build-folder>/ pi@fullpageos.local:extensions/<extension-name>/
Code contribution would be appreciated!
Top Related Projects
Lightweight justice for your single-board computer!
Scripts to build OctoPi, a Raspberry PI distro for controlling 3D printers over the web
A black hole for Internet advertisements
:beginner: Home Assistant Operating System
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot