You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.
Entering the same options e.g. --api-key every time can be tedious. There should be configuration options such as a dot-file and/or environment variables. Some initial thoughts:
As part of Smart portal selection skynet-docs#21 we should support system-wide configuration files with not just default portal selection but also connection options like --api-key etc.
We should also support environment variables as they are standard fare for cli applications. They should be namespaced with SKYNET_ e.g. SKYNET_API_KEY.
The priority of configuration should be as given here, that is, check first for cli options, then env vars, then config options.
Note: it is actually preferable to outsource these configuration responsibilities to the Go SDK itself. Every call from the CLI to the Go SDK will initiate a new client which should initialize the appropriate values based on the configs.
The text was updated successfully, but these errors were encountered:
Entering the same options e.g.
--api-key
every time can be tedious. There should be configuration options such as a dot-file and/or environment variables. Some initial thoughts:--api-key
etc.SKYNET_
e.g.SKYNET_API_KEY
.Note: it is actually preferable to outsource these configuration responsibilities to the Go SDK itself. Every call from the CLI to the Go SDK will initiate a new client which should initialize the appropriate values based on the configs.
The text was updated successfully, but these errors were encountered: