aska-digital · hydro-osچار مینار

hydro-os

The customization layer on top of Omarchy that makes charminar Shahid’s machine.

Stock Omarchy underneath. Every change we make lives here, tracked and guarded, so upgrades stay clean and the machine keeps working.

Pinned Omarchy 4.0.4 Machine charminar Team hydro-team

What it is

Not a fork. A thin, tracked layer over stock Omarchy.

hydro-os holds the changes that turn a stock Omarchy install into Shahid’s working machine, charminar. The base system stays untouched. Our blocks, launchers, and scripts live in this repo, marked so upgrades never collide with them.

Install

Clone it. Run the scripts as Shahid. Never as root.

terminal
# get the layer
git clone https://github.com/aska-digital/hydro-os.git
cd hydro-os
terminal
# apply a Hyprland block: removes the old block first,
# backs up, verifies, restores on failure
bash scripts/apply-hyprland-block.sh rhino-crm

# install an app-menu launcher
bash scripts/install-launcher.sh rhino-crm

The apply script verifies with Hyprland --verify-config before reloading. If verification fails, the backup is restored and nothing changes. New keybinds and window rules take effect on the next login, not on reload.

What’s inside

Five folders. Each has one job.

hyprland/

Guarded Hyprland config blocks, appended to the live config. Each block is marked at both ends so re-runs stay clean. SUPER+R opens the CRM. SUPER+C stays copy, always.

launchers/

.desktop files for the app menu, installed to ~/.local/share/applications. One file per app, named to match its block.

scripts/

One-time setup scripts. Apply a block, install a launcher. Guarded with backups and verification. Run as Shahid, no sudo.

docs/

Plain-language guides: the daily operating guide and safe hygiene commands. Written for the person at the keyboard, not just the maintainer.

apps/

Notes on what is deployed on charminar and where the real repos live. The apps themselves are not here. Their addresses are.

What does not live here

  • The CRM source code. That lives in aska-digital/rhino-crm, deployed to /home/muse/crm-os/.
  • Shahid’s personal data, the CRM database, backups, credentials, or Drive IDs.
  • Anything from stock Omarchy. We track our layer only.

The rules

Four rules. They protect the running machine.

  1. Never break the running CRM. The server at /home/muse/crm-os on 127.0.0.1:8741 stays up. The operating guide is the authority on what is safe.

  2. Hyprland changes go through the guarded-block pattern. Remove the old block first, append the new one, verify with Hyprland --verify-config, keep a backup.

  3. Test on charminar with Shahid around. Reboots and restarts are his call, not ours.

  4. Keep it small. Config here, patches to Omarchy itself never. Anything bigger is a fork discussion with Shahid first.

Source

hydro-os is maintained by the hydro-team for charminar. The repo holds the full layer: blocks, launchers, scripts, docs, and the pinned Omarchy version.

View on GitHub
← Back to ASKA Built by Aska Digital