my use case is very similar of the one in #975 where I'd like to have the main config file under git (possibly public), and the user stuff elsewhere, backed up separately.
atm I can't think of a sane way to have znc save to disk in a sensible way, unless another config option is added like SeparatedUserConf = true which removes the user and networks definition and move them to files named <datadir>/config/users/*.conf, but I'm not sure I'd call this sane.
my use case is very similar of the one in #975 where I'd like to have the main config file under git (possibly public), and the user stuff elsewhere, backed up separately.
atm I can't think of a sane way to have znc save to disk in a sensible way, unless another config option is added like `SeparatedUserConf = true` which removes the user and networks definition and move them to files named `<datadir>/config/users/*.conf`, but I'm not sure I'd call this sane.
This also kind of conflicts with #1030
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31950704-please-allow-the-configuration-to-be-spread-over-multiple-files?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:141298388 -->
I think it'd make sense to move user configs to users/<username>/user.conf, and network configs to users/<username>/networks/<networkname>/network.conf. It'd make it easier to have the main config under confuguration management or version control, and it'd also make it easier to move users between ZNC instances, which IMO would be very nice to have.
I think it'd make sense to move user configs to `users/<username>/user.conf`, and network configs to `users/<username>/networks/<networkname>/network.conf`. It'd make it easier to have the main config under confuguration management or version control, and it'd also make it easier to move users between ZNC instances, which IMO would be very nice to have.
<!-- github-comment-id:406524762 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
my use case is very similar of the one in #975 where I'd like to have the main config file under git (possibly public), and the user stuff elsewhere, backed up separately.
atm I can't think of a sane way to have znc save to disk in a sensible way, unless another config option is added like
SeparatedUserConf = truewhich removes the user and networks definition and move them to files named<datadir>/config/users/*.conf, but I'm not sure I'd call this sane.This also kind of conflicts with #1030
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I think it'd make sense to move user configs to
users/<username>/user.conf, and network configs tousers/<username>/networks/<networkname>/network.conf. It'd make it easier to have the main config under confuguration management or version control, and it'd also make it easier to move users between ZNC instances, which IMO would be very nice to have.