Multiple Server Suppport

[dasunsrule32]

Would be cool to aggregate and use this across multiple servers into a single linux-dash dashboard, and be able to drill down into each system and have some top level graphs.

[MartinBrugnara]

👍

[lsferreira42]

Agreed!

[thebouv]

Love this idea.

Lots to think about of course. Just a random amount here:

1. I wouldn't install this app on a production system unless it was password protected.
2. Given Small typo in demo header #1, we need to handle authentication if we're querying other systems.
3. Given fix typo in index.html #2, which authentication system do we use that's secure?

Fun stuff to think about though.

[dasunsrule32]

Or could just use key based authentication, which would be even better :)

[thebouv]

Even better. Let's make sure it works over telnet.

I KEED. :)

[Philzen]

For me SSH key access would be all that's needed - compare gitlab / github access management. Implementation is a no-brainer i believe.

I do realize currently Linux-Dash is pretty much configuration-file-free, but what if we offered to do the following:

• add a config.json file in root or /sh folder - actually maybe better to have a return array() php-include file in a protected location (as the php process will be the only actor invoking the data)
  • key names could be the same as in a ssh config file
  • on systems where the ssh config / ssh-agent are configured and accessible by the web service process, stating host alias(es) can be suffient
• Gathering the information should be a one liner ssh / bash - wrapping any original statements and executing them remotely

@afaqurk what do you think - useful? If anybody's interested, maybe i can help here or there.

@thebouv password protection is a whole (large) implementation area on itself - which is so easily worked around with an .htaccess (example with BasicAuth:)

AuthUserFile /somepath/.htpasswd
AuthGroupFile /dev/null
AuthName "Some cool monitoring tools not for everybody's eyes"
AuthType Basic
<Limit GET POST PUT>
require valid-user
</Limit>

That's just one of the possibility of doing it quick and dirty w/o adding a full-blown authorization & authentication framework to the application (at least not yet already ;) )

[tariqbuilds]

@Philzen - I'm not sure multiple server support naturally meshes with the setup of this (very simple) server monitoring dashboard. However, it is a cool concept I'd like to explore.

I have created a new branch: multi-server-support where I will be experimenting with the implementation. I encourage everyone to contribute. I certainly can not do it all alone.

As for built-in security, that is off the table for now. I would like to focus on other features and bugs first.

[LIONEFAN]

Hi @tariqbuilds,

The branch multi-server-support can't be found. I am looking for the solution about multiple servers support, how is this work going?

Thanks.