Command line args to disable config dialog and console about cloudcmd HOT 9 CLOSED

Ability to hide config landed in v5.8.0.

from cloudcmd.

Hi @jojow,

I'll think about it, this can have sense, can you tell me please how are you use Cloud Commander?

from cloudcmd.

I'm currently using Cloud Commander in a research project, dealing with complex simulation workflows in the field of e-science. More specifically, I'm working on a concrete use case, which requires to manage input and output files for a particular workflow.
Therefore, Cloud Commander is a great fit to manage the input/output files, by uploading/downloading files or transferring files from existing cloud storage.
However, it would be extremely helpful to strictly limit access of a Cloud Commander instance a particular directory, e.g. the user's home directory, so it's not possible for the user to access other files on the system. This is already possible by setting the "--root" argument, for example. However, the problem is that you can change the root directory at runtime through the config dialog. Thus, it would make a lot of sense for this use case to disable the config dialog completely, so the user does not have any chance to change the settings at runtime.
Same is true for the console, through which you have access to the entire filesystem.

I'm pretty sure that this would be helpful for other usage scenarios, too. This would also help to safely run several instances of Cloud Commander on the same host, each with its very own root directory.

from cloudcmd.

There is a couple things we should do to implementing this feature (I'll better write it down to not forget):

• add command line option to bin/cloudcmd.js
• add config check in middle ware lib/cloudcmd.js
• conditional show buttons in index.html and lib/server/route.js.

I do not know how better implement 3-rd step. Feel free to share ideas.

from cloudcmd.

Closed due to absence of ideas and time. I'll come back to this when ideas will come.

from cloudcmd.

This would be ideal for instances where you want to expose a directory on the webserver to multiple users without giving them inherent trust to browse your entire filesystem or change settings that will break things (port/auth/etc).

Cloud Commander is fantastic but seems that it's geared at a single, trusted, user scenario, when in reality we'd probably just use SSH for that as the sysadmins.

If this can ever be added it would be great!

from cloudcmd.

Added ability to hide config via --no-config-dialog option with b4c5b5a.

from cloudcmd.

Added ability to disable console with help of --no-console with c3c008f.

from cloudcmd.

--no-console landed in v5.9.0.

from cloudcmd.