Settings hostname and port in earls

[remagio]

I'm proposing a change in how earls manage httpd settings. Actually it sets only PORT, using default * for hostname (binding all local IPs).
Actually earls use in main():

app.listen(process.env.PORT || 3000);

It could be useful if it's using earls ENV if defined, by example:

EARLS_PORT=3000
EARLS_HOSTNAME="127.0.0.1"
…
…
app.listen(process.env.EARLS_PORT || 3000, process.env.EARLS_HOSTNAME || "" );
…
…

if I'm not mispelling and hostname not define it will use: *:3000 or *:EARLS_PORT

[edsu]

Does using PORT not work for you?

[remagio]

It's not my point, too many nodejs and python apps use default env PORT too. And it's missing the HOSTNAME env for setting httpd in nodejs/express (like my previous example). That's why I proposed EARLS_PORT & EARLS_HOSTNAME. Otherwise to force earls in using only "127.0.0.1" instead "*" requires to change standard earls.js source.

Initially I thought it could be better to use earls encoded in ENV names but starting in managing multiple instance of earls I think it's not enough. I tried out too in using "users" for isolation but it push more trouble for no sysadmin attitude.

I'm thinking to propose a new issue/enhancement b/c earls works very good and with a small footprint:

• Do not use the default redis in earls.js and make it clear to the users that they have to set it at their own risk on REDISTOGO. It will protects earls itself for redis's newbie;
• Introduction of an earls.conf like you did for anon to be sure that: at any time with any user it works with the right settings