[Feature Request]: split the $customRulesURL into a standard ruleset and a custom ruleset #80
Description
Please confirm:
- I have searched existing feature requests (open and closed) and found no duplicates.
Problem Statement
Current Problem:
When I fork the CyberDrain repo to add customer-specific rules, I'll constantly need to merge upstream changes from CyberDrain into my fork. This creates ongoing merge conflicts since my fork will diverge from the parent.
Desired Solution:
I want to maintain two separate ruleset URLs:
$rulesetURL - Points directly to CyberDrain's rules (no fork needed)
Stays automatically synced with upstream changes
No manual merging required
$customRulesetURL - Points to my own repo with only custom rules
Contains only my customer-specific additions
No merge conflicts with CyberDrain changes
Can be safely given to T1 techs for read/write access
This separates upstream rules from custom rules, eliminating merge overhead.
Benefits for MSPs
Reduce manual work for T3 techs and fork maintainers.
Improves customizability
Value or Importance
nice to have feature so that my custom json rules don't get lost