Repository navigation
nerdit v0.7.2
Nerdit v0.7.2 — local AI PaaS node.
Install
curl -fsSL https://get.nerdit.ai | sh
nerdit link NL-XXXX-XXXX
Pin this version with NERDIT_VERSION=0.7.2.
Assets
| file | platform |
|---|---|
nerdit-0.7.2-linux-x86_64.tar.gz |
Linux x86_64 (glibc 2.35+) |
nerdit-0.7.2-linux-arm64.tar.gz |
Linux arm64 (glibc 2.35+) |
nerdit-0.7.2-macos-arm64.tar.gz |
macOS arm64 (Apple silicon) |
SHA256SUMS covers the three tarballs; SHA256SUMS.sig is an
ECDSA P-256 signature over it, made with the key published below and as
the asset nerdit-release.pub.pem. The installer verifies both
before extracting. To check by hand:
sha256sum -c SHA256SUMS
openssl dgst -sha256 -verify nerdit-release.pub.pem \
-signature SHA256SUMS.sig SHA256SUMS
Release public key
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAErD99ocEK39T60IgnOpitYeNoHD+V
qwskFP+Z5xTkEFhI+zNwUBr06bBcVTzBH71xc472T0ZHRrr5aK6evs6oSg==
-----END PUBLIC KEY-----
Installer
The curl | sh installer for this tag has sha256 7dfb09f68dee378529ab54e39f72f96d11691cc24fea357226ce1891c95195fd.
To check what get.nerdit.ai served you:
curl -fsSL https://get.nerdit.ai -o install.sh
sha256sum install.sh
Changelog
VM templates close their own ports, and the texts say who can open a private
share.
Installation
- VM templates close their own ports. A template built with
install.sh --templatenow blocks connections from outside the machine to
Nerdit's HTTPS port (8443) and API port (9321), over TCP and UDP (HTTP/3),
IPv4 and IPv6, through the host's ufw firewall at every start. Apps stay
reachable through their hosted links, and containers still reach databases
and models. Machines cloned from an older template are unchanged until they
are recreated from a new one. The rule needs ufw to be active, so check from
outside the machine that both ports are closed, over TCP and UDP.
nerdit uninstallremoves the template's new unit drop-in, but the firewall
rules it already added stay: on a machine that keeps running, remove them
withufw delete deny proto tcp to any port 8443,9321and the same command
withudp.
Docs and help text
- Who can open a private share. The
nerdit share --publichelp, the
dashboard's share card, theshare_serviceMCP tool description, the API
field descriptions and the README now describe a private hosted share as
open to the owner of the machine's Nerdit account and the people they allow
in the Nerdit App, where they used to say the machine's owners only. Nothing
changes in behaviour on the machine: no command, option, API field or
default changed, and who may come in is decided in the Nerdit App.
Full history: CHANGELOG.md at tag v0.7.2 in the Nerdit source repository.
Source
Built from the public source tree at a5ca552cd993b9416d26deab8b39ddd48e0c830c.
The release tag points at this commit. Build instructions are in packaging/README.md.