77ko

There are many ways to do what herdr does, like tmux, and rex, but in a nutshell:

You launch cli things (claude code, cli tools etc) anywhere inside a herdr process. On your own laptop you magically stay connected to all of them and can monitor, send commands etc. And those processes can talk to each other and control each other too if u want!

For a single person with herdr+tailscale, you can make your own evolving software thingamajig across all the possible computers u have access to (pls don't call it a factory, we didn't call your fingers a factory in the dinosaur days did we).

DHH has good taste - leaving besides application choices (some of which I changed, e.g <insert_browser> instead of Chromium, no 1password), the configuration defaults all make sense (coming from a mac) - especially the key bindings.

Arch Linux by itself is a bit scary and requires config to make it "nice" so basically Omarchy takes away all the choices and config learning / pain - this tweet is a good summary:

> I've poured in endless hours configuring Hyprland + Arch, GTK/QT theming/scaling, auxiliary apps, and more to give you a superb base that can either be taken as-is or used to keep tweaking.[1]

Tiling window managers are great - I have young kids using computers for their hw and they prefered this over mac - windows. Which suprised me as personally it is a much bigger change for me after decades of regular windows/mac window management.

Linux / Hyperland Pros:

- I had a old pc from 2014 - which I put a minimal fresh new install of windows 10 - and it has been dog slow enough that it was waiting to be replaced. After installing Omarchy (Arch + Hyperland) it's perfectly fast and usable.

Cons: 1. Its designed to be a single user setup - the idea being u use HD encryption and login straight to the one true user. So for a shared pc its not ideal - the way its currently configured I think you need to run the omarchy bash install script for each user and also update individually for each one - not ideal for a pc shared with kids.

Really interested to see where Omarchy ends up. Its also given my usability ideas for my mac.

Which would fit in with existing uv commands[1] like `uv add plotly`.

There is an exisiting `uv lock --upgrade-package requests` but this feels a bit verbose.

Some requests:

Add simple examples and more clarity to the publish docs.

I assume most ppl would prefer to deploy via github actions[1], which the docs currently just link to a complex deploy file - can you please add some more documentation on this, or add an example of the simplest possible deploy file?

Suggestion: is it possible to use a interface (like in vercel) to connect to a github repo and build/publish on changes?