nerdypepper
The federated code forge (https://news.ycombinator.com/item?id=50305573)
https://tangled.org/docs/self-hosting/indexer/
we have also stabilized lexicons, so if you are a selfhoster, you can expect to not require a breaking upgrade!
its undocumented at the moment but you push over https as well.
somebody has set up a git credential helper here: https://tangled.org/pds.dad/tangled-core/blob/feature%2Fgit-...
this problem could exist with any package manager, the go package manager is one example, where it allows specifying packages from any git url. we host a mirror of all git repositories on our infra, and serve that when the backing knot is down. you could choose to trust that and pull from there (verifying that the tarball has a known correct hash), the way the go package manager pulls from proxy.golang.org.
private repos are coming very soon, we have a working demo of private repositories.
soon, repos will be able to declare a contribution policy: presently its open to all (anybody can open an issue), but owners can choose to limit this to just contributors for example.
Fast single-box DeepSeek v4.1 Flash runtime
Spoonful: Static site generator written in Nix
Bez: Generating a browser engine from specs and tests
Tobi: Persistent terminal sessions across your devices
Slag: Scriptable, hot-reloadable GPUI framework
Run Your Own CI
CI Should Be Disposable
steps:
name: Do the thing
run: nix build .#
at any point, if my CI is down or i need to switch or i need to run builds locally, i can do so trivially.tangled.org!
Every fucking website: 2026 edition
Tinysub: Simple web player for subsonic compatible music servers
Jjc: Scriptable Alternative to Jj Split
selfhosted runners do not go down when our CI is down, its operates separately.