summaryrefslogtreecommitdiff
path: root/crates/arti-relay/src/config.rs
Commit message (Collapse)AuthorAgeFilesLines
* arti-relay: remove 'override_net_params' configSteven Engler2025-01-141-20/+1
| | | | | | | We think that for relays, the 'override_net_params' config option is overly broad and a footgun. We can always re-add this back later if we want to, but for now the focus will be on exposing specific config options for features that are okay to be changed by users.
* arti-relay: fix rust/clippy lintsSteven Engler2025-01-141-1/+2
|
* arti-relay: add rust/clippy lintsSteven Engler2025-01-141-0/+14
|
* arti-relay: remove `TorRelayConfigBuilder::from_directories`Steven Engler2025-01-131-27/+0
| | | | | I don't think we'll ever need this. Users will set the directories through the config file.
* arti-relay: add `LoggingConfig`Steven Engler2025-01-131-0/+40
|
* arti-relay: default config paths now use path resolverSteven Engler2025-01-131-0/+13
|
* arti-relay: added a base `CfgPathResolver`Steven Engler2025-01-131-5/+122
|
* arti-relay: impl `TopLevel` for `TorRelayConfig`Steven Engler2025-01-131-0/+4
|
* update `CfgPath::path` to use a `CfgPathResolver`Steven Engler2024-11-181-1/+3
| | | | | | | | | | | | | | | | This is a big change across multiple crates since there isn't a good way to break it up. This changes the signature of `CfgPath::path` to: ``` pub fn path(&self, path_resolver: &CfgPathResolver) -> Result<PathBuf, CfgPathError> { ``` Making this change means that our global `CfgPathResolver` needs to be stored in the 'arti-client' library instead of `tor-config-path`, and must be passed through to anything that calls `path` to expand the variables.
* tor-config: removed re-export of `CfgPath`Steven Engler2024-11-041-1/+2
| | | | | Also updated other packages to get `CfgPath` directly from `tor-config-path' instead of 'tor-config'.
* arti-relay: Fix cargo doc issuesDavid Goulet2024-10-101-1/+1
| | | | Signed-off-by: David Goulet <[email protected]>
* arti-relay: Remove the use of pub and pub useDavid Goulet2024-10-101-7/+5
| | | | | | | | | | | | | | | The "pub" and "pub(crate)" visibility in a binary crate is essentially the same except for the dead_code warning analysis which ignores "pub" but will warn at "pub(crate)". This should get fixed soon according to: https://github.com/rust-lang/rust/issues/74970 However, for now, lets catch all this dead code :). Part of #1674 Signed-off-by: David Goulet <[email protected]>
* tor-keymgr: Move config/arti.rs to config.rsGabriela Moldovan2024-10-081-1/+1
| | | | | | | | The config will soon contain secondary C Tor keystore configuration too, so the `arti` namespacing is about to stop making sense. I recommend reviewing this commit using `git diff --color-moved=zebra --ignore-space-change`
* tor-keymgr: renamed ArtiNativeKeystoreConfig to ArtiKeystoreConfigMorgan2024-09-201-2/+2
|
* relay: Add KeyMgr to TorRelayDavid Goulet2024-09-181-1/+20
| | | | | | | | | | | | This is the first step before creating relay key definition and storing them into a keystore. The KeyMgr should be passed on the ChanMgr in later commit so the ChanMgr can use it for the authenticated channel handshake. Part of #1604 Signed-off-by: David Goulet <[email protected]>
* tor-relay: add `ChanMgr` to `TorRelay`Steven Engler2024-09-031-0/+26
|
* relay: Add basic configuration and builderDavid Goulet2024-08-201-0/+151
This adds the basic TorRelayConfig object along a builder in order to create a TorRelay object. At this commit, the configuration object only holds a "StorageConfig" which is a simple starting point which will allow to expand to a KeyMgr and then a ChanMgr along more configuration. There is also no custom Error for the crate at this point. Fixes #1534 Signed-off-by: David Goulet <[email protected]>