daniel/furtka
1
1
Fork 0
Code Issues 1 Pull requests Projects 1 Releases 13 Packages Wiki Activity Actions
furtka/website/content/_index.md

34 lines
1.3 KiB
Markdown
Raw Normal View History

feat: publish public website at furtka.org Hugo static site with an intentionally minimal single-page copy — English default, German under /de/ — while the project stays pre-alpha. No CMS, no external theme, no webfonts, no external requests. System-UI sans on a paper-white / near-black palette with a deep crimson accent; a small wicket-gate SVG as the sole brand mark. Hosting: nginx on forge-runner-01 serves /var/www/furtka.org; the upstream openresty proxy terminates TLS so the VM itself only speaks plain HTTP. Deploy is ./website/deploy.sh (rsync + remote hugo --minify). One-time VM bootstrap in ops/nginx/setup-vm.sh.
2026-04-14 10:27:51 +02:00
---
title: "Furtka"
description: "Open-source home server OS — simple enough for everyone."
chore: release 26.8-alpha (power actions, supersedes orphan 26.7 tag) Adds Reboot + Shut down buttons on /settings, backed by a new POST /api/furtka/power endpoint that kicks a delayed `systemd-run --on-active=3s systemctl {reboot|poweroff}` so the HTTP response flushes before the kernel loses network. Both buttons open a native confirm dialog; after reboot, the page polls /furtka.json until the box is back and reloads itself. 26.7-alpha was tagged on 5d8ac63 but release.yml never fired for that tag (Forgejo race with the concurrent main push; re-push of the deleted tag didn't wake the workflow either). 26.8 supersedes it and carries the same open_url + Open-button content plus the power actions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 15:54:58 +02:00
status: "<span class=\"mono\">26.8-alpha</span> — work in progress"
feat: publish public website at furtka.org Hugo static site with an intentionally minimal single-page copy — English default, German under /de/ — while the project stays pre-alpha. No CMS, no external theme, no webfonts, no external requests. System-UI sans on a paper-white / near-black palette with a deep crimson accent; a small wicket-gate SVG as the sole brand mark. Hosting: nginx on forge-runner-01 serves /var/www/furtka.org; the upstream openresty proxy terminates TLS so the VM itself only speaks plain HTTP. Deploy is ./website/deploy.sh (rsync + remote hugo --minify). One-time VM bootstrap in ops/nginx/setup-vm.sh.
2026-04-14 10:27:51 +02:00
---
**Furtka** is an open-source home server OS.
docs(website): plain-language landing page with shipped/planned sections Speak to non-technical visitors: drop "x86", swap "domain" for "name on the network", and list concrete upcoming apps (photos, files, smart home, game streaming, media) so the page says something real instead of just "it's early". Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-15 12:24:58 +02:00
Boot from USB, click through a wizard, and any old computer
feat: publish public website at furtka.org Hugo static site with an intentionally minimal single-page copy — English default, German under /de/ — while the project stays pre-alpha. No CMS, no external theme, no webfonts, no external requests. System-UI sans on a paper-white / near-black palette with a deep crimson accent; a small wicket-gate SVG as the sole brand mark. Hosting: nginx on forge-runner-01 serves /var/www/furtka.org; the upstream openresty proxy terminates TLS so the VM itself only speaks plain HTTP. Deploy is ./website/deploy.sh (rsync + remote hugo --minify). One-time VM bootstrap in ops/nginx/setup-vm.sh.
2026-04-14 10:27:51 +02:00
turns into a private cloud for your household — with your own apps,
docs(website): plain-language landing page with shipped/planned sections Speak to non-technical visitors: drop "x86", swap "domain" for "name on the network", and list concrete upcoming apps (photos, files, smart home, game streaming, media) so the page says something real instead of just "it's early". Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-15 12:24:58 +02:00
your own name on the network, your own data.
feat: publish public website at furtka.org Hugo static site with an intentionally minimal single-page copy — English default, German under /de/ — while the project stays pre-alpha. No CMS, no external theme, no webfonts, no external requests. System-UI sans on a paper-white / near-black palette with a deep crimson accent; a small wicket-gate SVG as the sole brand mark. Hosting: nginx on forge-runner-01 serves /var/www/furtka.org; the upstream openresty proxy terminates TLS so the VM itself only speaks plain HTTP. Deploy is ./website/deploy.sh (rsync + remote hugo --minify). One-time VM bootstrap in ops/nginx/setup-vm.sh.
2026-04-14 10:27:51 +02:00
The goal is simple: **your dad should be able to set this up.**
docs(website): plain-language landing page with shipped/planned sections Speak to non-technical visitors: drop "x86", swap "domain" for "name on the network", and list concrete upcoming apps (photos, files, smart home, game streaming, media) so the page says something real instead of just "it's early". Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-15 12:24:58 +02:00
### What's coming next
- Apps for photos, files, smart home, game streaming and media
- Plainer language in the setup wizard
- Secure connection on your home network (no browser warning)
- Linking several servers together
### What works today
- Boot from USB stick and install Furtka onto the hard drive
- A wizard asks for name, user and network — done
- Then: open the control page in your browser
- First app: **file sharing on the home network** (everyone on Wi-Fi sees the folder)
- Install and remove apps with one click
docs(website): draft the two update bullets for "What works today" Held as HTML comments in both _index.md and _index.de.md so the next site update — after the next ISO test confirms the container-image update flow and the Furtka self-update flow on real hardware — is just stripping the comment markers, not rewriting the copy from scratch. Keeping the live site honest until we can say "this works": the Phase-1 per-app updater and the Phase-2 self-update pipeline are both in the tree and in CI, but they haven't booted from an ISO yet. Per the "only publish facts verifiable from repo or confirmed by user" convention, they stay off the public page until that test is green. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-16 14:30:35 +02:00
- Update an installed app with one click (pulls the newest container image)
- Update Furtka itself with one click — no reinstalling for new features
docs(website): plain-language landing page with shipped/planned sections Speak to non-technical visitors: drop "x86", swap "domain" for "name on the network", and list concrete upcoming apps (photos, files, smart home, game streaming, media) so the page says something real instead of just "it's early". Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-15 12:24:58 +02:00
We're two people building it in public on evenings and weekends.
It's early.
feat: publish public website at furtka.org Hugo static site with an intentionally minimal single-page copy — English default, German under /de/ — while the project stays pre-alpha. No CMS, no external theme, no webfonts, no external requests. System-UI sans on a paper-white / near-black palette with a deep crimson accent; a small wicket-gate SVG as the sole brand mark. Hosting: nginx on forge-runner-01 serves /var/www/furtka.org; the upstream openresty proxy terminates TLS so the VM itself only speaks plain HTTP. Deploy is ./website/deploy.sh (rsync + remote hugo --minify). One-time VM bootstrap in ops/nginx/setup-vm.sh.
2026-04-14 10:27:51 +02:00
Want to follow along? Write to <a href="mailto:hallo@furtka.org">hallo@furtka.org</a>.
Reference in a new issue Copy permalink