Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge dev #32

Merged
merged 26 commits into from
Jul 19, 2024
Merged

Merge dev #32

merged 26 commits into from
Jul 19, 2024

Conversation

rasmus-kirk
Copy link
Owner

No description provided.

rlad78 and others added 26 commits March 31, 2024 10:27
Because initool cannot parse double-nested categories, sed is used
instead to edit sabnzbd.ini values. It also appears that SABnzbd will
keep any initial values written to sabnzbd.ini and then add any missing
keys with their default values. Therefore, we can just generate the bits
of config we need and let SABnzbd do the rest on its first run.
The Python configobj library is what SABnzbd uses to create and modify
their ini config file. Figured it'd be easiest to do the same, at least
for when we need to make changes after the initial config file has been
copied.
Passthrough the credentialsFile transmission option
Let api keys be generated by SABnzbd on first run; there's no point in
trying to do this ourselves. That effort was originally made when we had
confidence in generating the whole config file from scratch.
WIP: SABnzbd module for usenet integration
@rasmus-kirk rasmus-kirk merged commit fa2f0b0 into main Jul 19, 2024
1 check passed
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.

3 participants