m3kh / momo Goto Github PK

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.

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.