Ricing is an integral and fun part of the Linux community. But while the idea is exciting, the implementation often isn’t.
You see a beautiful rice on the internet. The author even shares their GitHub repository. You clone it, copy the configs manually, install the dependencies… and still end up wondering why it doesn’t look or behave the same as the author’s setup.
RIXI aims to solve this problem.
RIXI is a small, compact utility written in Rust that helps manage rices and configuration setups seamlessly. Instead of manually copying configs and guessing dependencies, RIXI uses a predictable directory structure to apply and manage rices in a clean, reproducible way.
Today, sharing your setup usually means creating a GitHub repository, documenting dependencies, and writing an install.sh script and hoping it works on someone else’s machine. Even then, things break. Things always break. 
With RIXI, the goal is to simplify this. Instead of maintaining a full repository, you could simply run:
rixi push <author>/<theme>
and make your rice available for the community to discover and use.
Stop copying. Start RIXI.
(Sorry for the low-res gif, compression issues :P)
Also… RIXI doesn’t have a logo yet. If anyone in the community
is kind enough to design a tiny 8-bit pixel mascot, I’d love to include it.
Checkout the project here - Github.
