Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/didiatworkz/screenly-ose-monitoring
Manage multiple Screenly OSE Player in one web Interface
https://github.com/didiatworkz/screenly-ose-monitoring
assets control digital-signage information interface monitoring multi ose php pi player raspberry raspberry-pi-3 raspberry-pi-4 screenly screenly-ose signage somo upload website
Last synced: 4 months ago
JSON representation
Manage multiple Screenly OSE Player in one web Interface
- Host: GitHub
- URL: https://github.com/didiatworkz/screenly-ose-monitoring
- Owner: didiatworkz
- License: mit
- Created: 2018-10-09T16:44:25.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-12-24T15:06:57.000Z (about 3 years ago)
- Last Synced: 2024-09-28T10:20:12.750Z (4 months ago)
- Topics: assets, control, digital-signage, information, interface, monitoring, multi, ose, php, pi, player, raspberry, raspberry-pi-3, raspberry-pi-4, screenly, screenly-ose, signage, somo, upload, website
- Language: JavaScript
- Homepage:
- Size: 54 MB
- Stars: 106
- Watchers: 17
- Forks: 30
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# Screenly OSE Monitoring (SOMO)
![GitHub Repo stars](https://img.shields.io/github/stars/didiatworkz/screenly-ose-monitoring?color=lightgrey&style=for-the-badge) ![GitHub release (latest by date)](https://img.shields.io/github/v/release/didiatworkz/screenly-ose-monitor?style=for-the-badge) ![GitHub Release Date](https://img.shields.io/github/release-date/didiatworkz/screenly-ose-monitor?style=for-the-badge&color=green) ![GitHub commit activity](https://img.shields.io/github/commit-activity/y/didiatworkz/screenly-ose-monitor?style=for-the-badge) ![GitHub issues](https://img.shields.io/github/issues-raw/didiatworkz/screenly-ose-monitor?style=for-the-badge)
![GitHub Workflow Status](https://img.shields.io/github/workflow/status/didiatworkz/screenly-ose-monitoring/Docker%20Image%20CI?style=for-the-badge&label=Docker%20image) ![Docker Image Size (tag)](https://img.shields.io/docker/image-size/atworkz/somo/latest?style=for-the-badge&label=atworkz%2Fsomo%3Alatest&logo=docker&logoColor=white) ![Docker Pulls](https://img.shields.io/docker/pulls/atworkz/somo?style=for-the-badge)
- [Intro](#what-is-this)
- [Features](#features)
- [Bugs](#Bugs)
- [Requirements](#requirements)
- [Installation](#installation)
- [Login](#login)
- [Update](#update)
- [Changelog](#changelog)
- [More Questions?](#any-more-questions)## What is this?
Screenly OSE Monitoring is a web-based application that is simultaneously installed on a Screenly OSE Player or as standalone server solution.
With this tool, you can manage multiple Screenly OSE players in one web-interface.
In addition to its current display status, you can also manage the assets of a player. It is possible to activate or deactivate assets, add new ones, edit or simply delete them all from the player.
Also it's possible to reboot the player directly or upload new assets to multiple players parallel.
By installing an add-on on each player, it is also possible to display a "live feed" of the player's HDMI output and live-data from the system. This will then be displayed in the overview, as well.## Features
+ Easy administration
+ Dashboard
+ User management
+ Group access management incl. access restrictions
+ Simple overview of all players with status
+ Add / Edit / Remove / Order / Switch Assets
+ Auto discovery of players in a subnet
+ Upload assets simultaneously to multiple playes
+ Group players
+ Responsive Design
+ Dark and Light Mode
+ Public access to integrate in other monitoring tools
+ Add-on overview of all players
+ Add-on for displaying the player’s output remotely
+ Add-on for displaying the player’s system information__SOMO v4.2 tested on Raspbian buster and bullseye__
## Bugs
No errors were found in the tests. If you find a problem or bug, please report it:
[Open Issue List](https://github.com/didiatworkz/screenly-ose-monitoring/issues?q=is:issue%20label:bug)---
## Requirements
+ RaspberryPi 3B+
+ Raspbian Lite Buster
+ Docker (will be installed)## Installation
__IMPORTANT: The monitoring was designed to run on the local network with the Screenly OSE Player. Problems or restrictions may occur if the server is hosted externally or accessed from an external network!__Very simple installation:
1. Connect to the player via SSH or terminal ([CTRL]+[ALT]+[F1])
2. Copy this line and execute it
```sh
bash <(curl -sL https://git.io/JttTW)
```
3. Answer the questions and installation will be start (This may take a while - Don't worry)
4. Open your Browser to the IP address of the Raspberry Pi like: http://[screenly-ip-address]:9000## Login
After the installation is the default login:http://[ip-address]:9000 (when Screenly OSE is installed)
http://[ip-address] (Server installation)Username: demo
Password: demo
---
## Update
For the update you only have to run the installer again.
The installer checks if there is an old installation and saves it if necessary.
From version 2.0 there are changes to the database structure which is prepared for future updates and no longer needs to be saved.But please note that the Add-on may have to be reinstalled on the players. (Current for all older versions before version 2.0)
__IMPORTANT: If monitoring is installed on a Raspberry Pi that does not have a Screenly OSE Player (standalone installation) the port changes from 9000 to 80.
So the monitoring is accessible via the normal IP address!__### Update SOMO
```sh
bash <(curl -sL https://git.io/JttTW)```
### Update Extension
Link via Monitoring or here:
```sh
bash <(curl -sL https://git.io/Jf900)
```### Changelog
[Open Changelog](https://github.com/didiatworkz/screenly-ose-monitoring/blob/master/CHANGELOG.md)
## Any more questions?
There's something else that wasn't answered here?
Then just have a look at the [wiki-page]([https://github.com/didiatworkz/screenly-ose-monitoring/wiki](https://github.com/didiatworkz/screenly-ose-monitoring/wiki)). Maybe you will find an answer there.Thanks for using this project!
\- didiatworkz