Enonic CLI - Remotes

[pmi]

https://github.com/enonic/enonic/blob/master/xp/7.0/enonic-cli.md#remote-commands

[pmi]

Connection params which are:

• auth
• host
• port
• scheme

They should be saved along with a connection name to ~/.enonic/.enonic under remotes header. Following sub-commands will be used to manage remotes:

• add [name] [scheme:][//[user:pass@]host:port]
• remove [name]
• set [name]
• ls

default http://localhost:8080 should be always present and impossible to delete

[GlennRicaud]

Not sure about saving [user:pass] in clear text in a file. That is why I wanted to know if it was like a connect or more like a list of remote URLs.

If we want to have this user password, then maybe keeping the session ID would be better. Or some other solution. To be discussed

[pmi]

@GlennRicaud True, I thought about storing passwords in a hashed and salted way But in this case backend needs to be modified to accept it this way of course.