Community dogs
metrics and bark ship inside the shep binary. Everything below is a dog someone outside this project wrote and adopted the same way, with shep adopt <path>, pointed at a binary you didn't have to write yourself.
You can read the same index from a terminal: shep dogs --available prints the install and adopt commands below, narrowed with an optional filter.
Being listed here means three things and nothing more: the repository is real, the license is open, and the thing is genuinely a dog. Nobody on this project reviewed the code, audited it, or is vouching for it. Adopting one runs it at the shepherd's own trust level, the same as anything else your Flockfile already starts.
One assumption runs through every entry below: a crate's binary doesn't have to share its package name, and CARGO_INSTALL_ROOT or GOBIN can move where the installer puts the file, so check where it actually landed before adopting it. Getting the path wrong is loud, since shep adopt refuses a path that isn't there. Getting the name wrong is silent, which is exactly why adopt_as exists as its own field instead of reusing the package name.
Logs
shep-log-rotate (Bella)
Rotates grown log files and asks the shepherd to reopen them.
$ cargo install shep-log-rotate $ shep adopt ~/.cargo/bin/shep-log-rotate --name log-rotate
Deploy
shep-deploy (Moon)
Watches a git branch, builds a release in an isolated directory, swaps to it, and rolls back on its own if the new release does not come up.
$ cargo install shep-deploy $ shep adopt ~/.cargo/bin/shep-deploy --name deploy
Add a dog
Add yours by editing web/public/dogs.json and opening a pull request. Point your editor at the published schema and it will tell you what an entry needs while you type it. The build runs its own validator over every entry before the site ships, and a test keeps the two in step, so a pull request that satisfies the schema will not surprise you in CI.