Ninja Build VS Oxidized

Under the hood, Rescript uses a build system called Ninja. Ninja is similar to Make, but cross-platform and more minimal/performant. - Source: dev.to / 3 months ago

Ninja was super easy to pick up even after using make for some time (10+ years). GN is just a ninja generator that is optional. https://gn.googlesource.com/gn/+/main/docs/quick_start.md https://ninja-build.org/. - Source: Hacker News / 4 months ago

Really? I thought most new projects were switching to ninja[^1] and have never used it. [^1]: https://ninja-build.org/. - Source: Hacker News / 7 months ago

Ninja showed real promise for a while, but then CMake grew up and people stopped seeing a reason to leave it behind. Source: 10 months ago

Now that you have your build system all generated you can go ahead and build everything. By default Meson will use Ninja as the build tool. Ninja is similar to Make but much much faster. You can also generate additional build systems but that's outside of the scope of this post. - Source: dev.to / about 1 year ago

Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized. Source: about 1 year ago

You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email. Source: about 1 year ago

RANCID was great before Oxidized ;) Https://github.com/ytti/oxidized From description of Oxi: Oxidized is a network device configuration backup tool. It's a RANCID replacement! Source: over 1 year ago

If you're just looking to backup/inventory configs, give Oxidized a try https://github.com/ytti/oxidized. Source: over 1 year ago

What about the tried and trusted oxidized? Source: over 1 year ago