m3kh / momo

Simple RaspBerry Modular dashboard

momo

Multi flavour Entretaiment Raspberry pi

---

Entretaiment

This is a project co-related with an image for the SD of the RaspBerry

Solutions Provided

• A media center throught Kodi.
• A game center with Emulstation and RetroRaspberry (include also a Virtual Joystick).
• A airplay server to use your raspberry to transmit your music.

Installation

---

I'm shipping this project together with the image for the Raspberry, in the otherhands you can follow the same steps to install all the required packages in your favorite distro.

Install RetroPie

[Retropie Setup] (http://blog.petrockblock.com/2012/07/22/retropie-setup-an-initialization-script-for-retroarch-on-the-raspberry-pi/)

sudo apt-get update
sudo apt-get install -y git dialog
cd
git clone git://github.com/petrockblog/RetroPie-Setup.git
cd RetroPie-Setup
chmod +x retropie_setup.sh
sudo ./retropie_setup.sh

Install shairport-sync

ShairPort Setup

Install Kodi

Kodi

Chrome on start up

http://blogs.wcode.org/2013/09/howto-boot-your-raspberry-pi-into-a-fullscreen-browser-kiosk/

momo's Issues

More pluggable structure

Momo should be the barebone of the skeleton. And right now is just one piece.

His functional health status is strict related to the environment where is executed, since requires some dependencies to be installed.

Ideally this situations should be turned around and get a situation where:

• We store the current configurations for the installed momo under ~/.momo in a json format.
  
  Where we can store something like:
  • Current installed plugins
  • Service Name (Useful for some settings and expositions of some services)
• We provide a template for the Plugin, which identify his workflow on the App runtime:
  • Service side:
    • BeforeInstall
    • Install
    • Run
    • Stop
    • BeforeUninstall
    • Uninstall
  • Ui side:
    • Add button or other ui elements
    • Custom remote ui
    • Custon dasboard ui
  • A Configuration file
    • Contains systems compatibilities, to enable to be installed only in certain OS
    • Requirements for other Plugins, or services.
    • Dependency with optionals filters based on OS
    • Ask for root run permissions if is needed (display a confirmation dialog before install)
• We deliver shortcuts/methods for:
  • Identify the OS where runs to provide strategies on the Plugin Workflow
  • WGet/Git/Apt-get download methods to install sub binaries or other dependencies
  • Start/Stop Services
  • Bind to events
  • Write/Read Global Configs, Plugin Configs, File Configs.
  • Run commands
  • And still be able to use the power of node ecosystem.

---

If everything would be in place, the functionalities can be split in different repositories.

Add functionality to change configurations files

Since is useful for instance for change hdmi_mode in /boot/config.txt, this feature can be thought more generic.

The first scope should be able to get a minimal of ui + node utils to parse config texts.

In mind should be keep the visions that this feature can be useful to modify generics configurations files like: /etc/lighttpd/lighttpd.conf, /etc/shairport-sync.conf or other services configs.