[PR #551] Add Rudder to Configuration Management #1184

New Issue

GiteaMirror · 2025-11-19T21:10:17-06:00

GiteaMirror commented

2025-11-19 21:10:17 -06:00

Original Pull Request: https://github.com/awesome-foss/awesome-sysadmin/pull/551

State: closed
Merged: Yes

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
[n/a] Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

Why is it awesome?

Rudder is, in effect, a pretty CFEngine frontend, and has the ability to interact with the systems it manages on a pull-based system, rather than a push (Though you can push, if you so desire). It's awesome because it scales easily, is extremely reliable (in my experience) and very easily extensible with your own directives, groups, rules and script packages.

Have you used it? For how long?

Yes, for around 6 years.

Is this in a personal or professional setup?

Both, I've had it in my lab managing 20+ Linux systems for years, but have also implemented it at scale with multiple relays in a 500+ endpoint environment.

How many devices/users/services/... do you manage with it?

Personally? 23 currently.

Biggest pros/cons compared to other solutions?

Honestly? Ease of use if you're coming from an RMM with agent procedures like Kaseya. Reporting is a piece of cake with the really well documented API, and the agents are extremely reliable being based on CFEngine.

Biggest con is that the server is a bit of a resource hog on larger installations.

Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

Only limitation I can think of is that the automated patch management and compliance modules that have prebuilt scripts for CIS, ISO27k etc have a price tag. This does not mean you can't just build them yourself, though.

**Original Pull Request:** https://github.com/awesome-foss/awesome-sysadmin/pull/551 **State:** closed **Merged:** Yes ---  Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [x] Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [x] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [n/a] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can:  - **Why is it awesome?** Rudder is, in effect, a pretty CFEngine frontend, and has the ability to interact with the systems it manages on a pull-based system, rather than a push (Though you can push, if you so desire). It's awesome because it scales easily, is extremely reliable (in my experience) and very easily extensible with your own directives, groups, rules and script packages. - **Have you used it? For how long?** Yes, for around 6 years. - **Is this in a personal or professional setup?** Both, I've had it in my lab managing 20+ Linux systems for years, but have also implemented it at scale with multiple relays in a 500+ endpoint environment. - **How many devices/users/services/... do you manage with it?** Personally? 23 currently. - **Biggest pros/cons compared to other solutions?** Honestly? Ease of use if you're coming from an RMM with agent procedures like Kaseya. Reporting is a piece of cake with the really well documented API, and the agents are extremely reliable being based on CFEngine. Biggest con is that the server is a bit of a resource hog on larger installations. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** Only limitation I can think of is that the automated patch management and compliance modules that have prebuilt scripts for CIS, ISO27k etc have a price tag. This **does not** mean you can't just build them yourself, though.

GiteaMirror added the pull-request label 2025-11-19 21:10:17 -06:00

GiteaMirror closed this issue

2025-11-19 21:10:18 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#1184