Skip to content

Conversation

@irbull
Copy link
Contributor

@irbull irbull commented Jan 24, 2026

Add ability to configure daemon.auto-sync, daemon.auto-commit, daemon.auto-push, and daemon.auto-pull via config.yaml.

Priority order: CLI flag > env var > YAML config > database config

Individual YAML settings allow fine-grained control without triggering the legacy "enable everything" behavior. Tests cover unified and individual settings, env var overrides, and CLI flag overrides.

Add ability to configure daemon.auto-sync, daemon.auto-commit,
daemon.auto-push, and daemon.auto-pull via config.yaml.

Priority order: CLI flag > env var > YAML config > database config

Individual YAML settings allow fine-grained control without triggering
the legacy "enable everything" behavior. Tests cover unified and
individual settings, env var overrides, and CLI flag overrides.
@irbull
Copy link
Contributor Author

irbull commented Jan 25, 2026

Any thoughts on this? Essentially the problem is that the daemon needs to be started with the --auto-commit because it doesn't read it from the config.yaml. However, the daemon won't start with this setting if you have auto-start on. Took me a while to figure out how to even get this to work, because each time I killed the daemon (so I could start it with auto-commit) it automatically started without this setting.

There is bd config set daemon.auto-commit true but this just sets the flag in the config.yaml, which isn't read (until this is merged ;).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant