add beszel-agent startup arguments

[a-mnich]

I'm running the beszel-agent on Windows as a permanently running scheduled task in system context to avoid needing alternative programs like NSSM for running it in the background. As the Windows task scheduler provides support for supplying startup arguments I prefer to directly supply key and port via the commandline to be able to manage everything at one place.

Changes:

• Added support for -key and -port flags to allow users to specify the public key and port number directly from the command line.
• Updated the usage information to provide a clear guide on available options and subcommands.
• Modified the logic to prioritize the -key flag over the KEY environment variable and the -port flag over the PORT environment variable.
• Enhanced error messaging to include instructions for using the help subcommand when the key is not provided.
• changed the version command to version instead of -v to allign with the other command like help and update

[henrygd]

Thanks!

I need to refactor this section anyway as we're deprecating PORT in favor of ADDR. I'll merge this before I do that, probably tomorrow.

We'll likely go with -addr instead of -port, but no further changes are necessary to the PR 👍

[gedw99]

great I need this too for agent.

[gedw99]

Would be nice if the ENV's are prefixed with BESZEL_, so that we do not pollute Env namespace with other things running.

The flags dont need this, just the ENV names.

[henrygd]

@gedw99 This has been added. In the next release you can optionally prefix all env vars with BESZEL_HUB_ or BESZEL_AGENT_.

[gedw99]

@gedw99 This has been added. In the next release you can optionally prefix all env vars with BESZEL_HUB_ or BESZEL_AGENT_.

Sweet :) thanks @henrygd

[henrygd]

Merged, thanks 👍

[kenrmayfield]

@a-mnich

Can you provide the Steps for Settting Up the Beszel Agent in the Windows Task Scheduler?

[a-mnich]

@a-mnich

Can you provide the Steps for Settting Up the Beszel Agent in the Windows Task Scheduler?

See #570