Startup and process manager review

[taboca]

With Tela Social 1.0, the approach for the always running architecture was broken down in two things:

• A cron script, which calls a client browser engine - every one minute. Such client browser is called through its binary via startx, so it's assumed that X infrastructure is ready to go for the process user.
• A nodejs script that is started from traditional init.d infrastructure using a process manager system, Forever.

New architecture

This new architecture is a proposal and it needs heavy testing.

• It's assumed that the X infrastructure is existing, and that an X server is running to accept connection from scripts that wants to export to the X screen :0
• A startup script, init.d or service (upstart), will launch a stronger process manager for Node. The process manager should offer support to upstart or init.d scripts;
• The browser will be launched from a node that is responsible for managing always one browser in the screen and executing basic browser checkups;

[taboca]

Considerations and dependencies with other projects

PM2

• We need to have DISPLAY environment variable set within the node, or associated with PM2 context, because PM2 will load the script from another context, not the current user shell;
• Startup scripts is supported by PM2 - http://pm2.keymetrics.io/docs/usage/startup/#command