Re-do the CLI again #405

gijzelaerr commented 2021年07月28日 09:24:05 +02:00 (Migrated from github.com)

the current CLI works, but can be more user-friendly

the current CLI works, but can be more user-friendly

jwijenbergh commented 2023年03月06日 16:12:39 +01:00 (Migrated from github.com)

The CLI has been rewritten, interactive mode "eduvpn-cli interactive" should be pretty user friendly but the normal CLI needs documentation

The CLI has been rewritten, interactive mode "eduvpn-cli interactive" should be pretty user friendly but the normal CLI needs documentation

mmahmoudian commented 2024年10月27日 10:11:44 +01:00 (Migrated from github.com)

The interactive subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI.

Having manpage, infopage, better error and messaging and clarifying the steps for the sake of logging and finding the point of failure is what that can improve the CLI experience imho.

Maybe at some point I add manpage and add the missing documentation.

The `interactive` subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI. Having manpage, infopage, better error and messaging and clarifying the steps for the sake of logging and finding the point of failure is what that can improve the CLI experience imho. Maybe at some point I add manpage and add the missing documentation.

jwijenbergh commented 2024年10月28日 14:37:19 +01:00 (Migrated from github.com)

The interactive subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI.

That's exactly why it's been made, as an alternative to the GUI. For scripting there are a bunch of flags that you can use. The reason why I have not extensively documented these outside of --help is that I am not super happy with them. I think I have to rewrite the CLI again but this time make a document of how it should work beforehand

> The interactive subcommand is heavily missing the point of the major use-case of a CLI. The CLI is usually used for automation and scripting. Therefore, the interactive is useless in 100% of automation use-cases, and it is only and only helpful if one wants to use it as an alternative to GUI. That's exactly why it's been made, as an alternative to the GUI. For scripting there are a bunch of flags that you can use. The reason why I have not extensively documented these outside of `--help` is that I am not super happy with them. I think I have to rewrite the CLI again but this time make a document of how it should work beforehand

jwijenbergh commented 2025年10月29日 09:50:28 +01:00

Nothing concretely actionable here

Nothing concretely actionable here