Discussion is still in-progress concerning swh.core.config rework (T1410).
Description
Description
Revisions and Commits
Revisions and Commits
Related Objects
Related Objects
- Mentioned In
- D4218: docs: add configuration.rst
- Mentioned Here
- T1410: Kill implicit configuration: new configuration scheme
Event Timeline
Comment Actions
While we wait for a proper solution, I think there is nothing stopping swh fuse from loading a configuration file by default if it exists and -C is not passed on the CLI.
We should just move -C up one level (from swh fuse mount to swh fuse) and do something similar to what swh-scanner does.
The location of the file might change in the future as a consequence of T1410, but meh, it's not a big deal.
We can stay on the safe side for now and only support ~/.config/swh/fuse/fuse.yml. And we will worry about merging with a global config file later.