PengyOS / Docs / Recipes

Recipes

Short how-tos for common jobs. They work on the Server and Desktop editions (Core leaves out podman, curl and git). Every recipe installs into your home directory or a container, never into the read-only system.

Two facts every recipe relies on. ~/.local/bin is already on your PATH, so a binary you drop there is a command. And there's no C compiler on the host: anything that needs one to build runs in the dev box. Why?

Developing

The dev box

An Ubuntu 24.04 toolchain (gcc, cmake, Go, Rust, uv) in a container that shares your home. Exporting its apps to the host.

Python with uv

Projects, venvs, other Python versions and command-line tools, right on the host.

Rust with rustup

Build in the dev box, run on the host. Static binaries with musl.

Go

The upstream toolchain in ~/.local/go. Pure-Go builds work without the dev box.

llama.cpp

Build it in the dev box, run a model on the CPU or a GPU, point Pengy at it.

Services

Containers with podman

nginx and MongoDB, data that survives, starting at boot, opening the firewall, compose files.

Files & sync

Syncthing

Peer-to-peer folder sync between your machines, as a user service that starts at boot.

rclone

Sync and back up to S3, Backblaze B2, Google Drive and others. Mount a remote on the Desktop.

Missing something? These docs grow with what people actually do on PengyOS. The same four ways of adding software (explained here) cover almost anything.