subroutine connections

The 1 command under subroutine connections, each with its arguments and options.

subroutine connections [OPTIONS] COMMAND [ARGS]...

Not listed by subroutine --help.

List the instances this reaches, which one you are working in, and where each one's token came from.

No token is ever printed, and none can be recovered from what is. Which of the four places supplied it is the useful part — the standing footgun in comparable tooling is not having several sources but not knowing which one won.

subroutine connections add

subroutine connections add [OPTIONS] [name]

Record another instance this machine can reach.

Examples:

subroutine connections add work --url https://tasks.example.com

subroutine connections add work --url https://tasks.example.com --read-only

subroutine connections add acme --url https://acme.example --token-env ACME_TOKEN

The name is yours and nobody else's. It becomes the first part of every address that instance's items print as, so work/acme/42, and two people reaching one server may call it different things.

It asks for the token unless one is already set for that name, checks that the address and the token both work by reaching the instance, and writes nothing until they do. Tokens are kept in a file of their own that nothing else reads.

Arguments

• name (str): What to call it here, as in 'work'.

Options

• --url (str): Where that instance is, as in https://tasks.example.com.
• --token-env (str): Read its token from this environment variable rather than storing one.
• --token-command (str): Run this to get its token, as in a password manager's show command.
• --read-only (flag): Read that instance but refuse to write to it.
• --default (flag): Send new work there rather than to your own database.
• --check / --no-check (flag, default True): Reach the instance before recording it. On by default.