Skip to content

Latest commit

 

History

History
108 lines (65 loc) · 4.63 KB

README.md

File metadata and controls

108 lines (65 loc) · 4.63 KB
Raw

Obscreen

Obscreen is a user-friendly self-hosted digital signage tool leveraging chromium browser.

🕹️ Live Demo

Try it!

Demo Server (Location: Roubaix - France): https://demo.obscreen.io

It is a temporary live demo, all data will be deleted after 30 minutes (~30secs downtime).

⭐️ Features

  • Dead simple chromium webview inside
  • Fancy graphical user interface
  • Very few dependencies
  • Embeddable SQLite database
  • Fleet screen management
  • Playlist management
  • Authentication management
  • Plays content from flashdrive in offline mode
  • Plugin system to extend capabilities
  • Multi Languages
  • Cast pictures and iframes to Chromecast
  • No costly monthly pricing plan per screen or whatever, no cloud, no telemetry

👨‍🍳 Cookbooks

🔴 I want to power a RaspberryPi and automatically see my slideshow on a screen connected to it and manage the slideshow

🔵 I just want a slideshow manager and I'll deal with screen and browser myself

📸 More Screenshots

Light Mode:

Content Explorer:

Settings Page:

Add Content Modal:

🫡 Motivation

  • I was searching for a self-hosted monitoring tool similar to "Screenly", but struggled with "Anthias" (formerly Screenly OSE) due to compatibility issues on some webpages. Chromium does a great job at rendering webpages, so I decided to create my own solution based on browsers.
  • Enjoy a beautiful graphical interface
  • My goal was to keep the code as simple as possible, using reliable technology with minimal dependencies.
  • Aim to showcase the power of the Raspberry Pi 5.
  • Deploy my first true Docker image to Docker Hub using a continuous deployment pipeline.

If you value this project, please think about awarding it a ⭐. Thanks ! 🙏

🛟 Discussion / Need help ?

Join our Discord

Open an Issue

Troubleshoot

Videos aren't playing why ?

This is "normal" behavior. Videos do not play automatically in Chrome because it requires user interaction with the page (a simple click inside the webpage is enough). If you open the console, you'll see the error: Uncaught (in promise) DOMException: play() failed because the user didn't interact with the document first...

To resolve this, you need to use the Chrome flag --autoplay-policy=no-user-gesture-required. When connecting a Raspberry Pi with Obscreen Player autorun, this issue doesn't occur because the flag is handled automatically for you.You need to enable this flag yourself otherwise.

👑 Contributions

Create Pull Requests

We accept all types of pull requests.

Test Beta Version

Check out the latest beta release here: https://github.com/jr-k/obscreen/releases

Translations

If you want to translate Obscreen into your language, please visit Languages Files.

Spelling & Grammar

Feel free to correct the grammar in the documentation or code. My mother language is not English and my grammar is not that great.