| wiki | home | irc | git | files |
reference wiki for druid.rocks's public-facing services, and a small open knowledge base anyone with an account can add to. not a database-backed wiki app - pages are plain btf source (the same tool the rest of the site is built with), uploaded over rsync/sftp (no git push required to publish - see "getting an account" below) and rebuilt on a 5-minute cron.
irc - connecting to irc.druid.rocks, now public.
git - cloning repos off git.druid.rocks.
files - pulling bulk files off files.druid.rocks.
only services with something worth telling a stranger get a page here. cc.druid.rocks, the dev/compile nodes, and mp.druid.rocks (which already has its own docs site) don't.
anyone with an account can write pages under pages/ - that's the actual open, collaborative part of this wiki, shared by everyone who has one. the reference pages above are hand-maintained separately and aren't part of that shared tree.
everyone with an account also gets a personal sandbox under u/<name>/, theirs alone - nobody else can write there, and it never gets mixed into pages/.
register on irc.druid.rocks (self-service, `/REGISTER <email> <password>` once connected), then ask for a wiki account. there's no signup form - an account is one command on this end (`wikiadd <name> <your pubkey>`), so it's quick once asked for, but it's not automatic and isn't meant to be: this keeps a real person in the loop before anyone gets write access to the domain.
whoever sets your account up sends you the exact connect details (host/port and a small ssh config snippet) directly, not posted here - the ssh key is what actually gates access, not port secrecy, but there's no reason to broadcast it publicly either. once you have those details, publishing is one rsync command:
rsync -avz --rsh="ssh -F ~/.ssh/config" mypage.btft wiki-pages:for the shared knowledge base (lands in pages/), or the same thing against your own personal alias for u/<name>/. either way: wait up to 5 minutes for the rebuild cron, or just check the site. a broken page never takes down the rest of it - the old version stays up until it's fixed.
keep it lowercase, keep it short, and explain why something is the way it is instead of just what it is. no marketing tone, no "welcome to our wiki!" - this is a reference, not a pitch.
pages are btf source (.btft), the same format used for mp's docs and the main site. don't guess the syntax from scratch - read one of this wiki's own .btft source files (they're plain text, same as anything you'd upload) or anything under mp's docs/ tree for real, working examples: headings, paragraphs, links to other pages on the same site, links elsewhere, tables, and fenced code all show up there in context.