Think sadservers.com but focused on "bring your own scenarios and hw" (which will be realized later down the road)
09.03.2026 00:05
👍 0
🔁 0
💬 0
📌 0
Think sadservers.com but focused on "bring your own scenarios and hw" (which will be realized later down the road)
Real-world scenarios. My test scenario is a broken nginx, where you have to fix 3 different things:
* Bring the nginx service back to a healthy running state.
* Restore the default nginx site configuration.
* Make sure the service is reachable on port 80.
We're having a breakthrough!
Users are now able to run missions (e.g. fix a broken nginx server) in isolated VMs. After successfully finishing the mission, the user can see an asciicast replay of the commands used.
Now I'm looking for a way to properly build the missions.
#buildinpublic #rustlang
Doing a lot of progress :)
intar.dev now has a small buildlog
- latest achievement is asciicast of the SSH session :)
#rustlang #buildinpublic
Flying to London for @rustnationuk.bsky.social
Hacking on @intar.dev the coming days. Already got VM creation, auto-reaping and @netbird.bsky.social setup working.
Next tasks will be:
* Self-hosting NetBird
* Setup bare-metal server
* Deploy agent and connect it to the website
#buildinpublic
Watch www.youtube.com/watch?v=wpIm... if you want to know a bit more about intar :) I show @rawkode.dev what the CLI is able to do right now
Visit github.com/intar-dev/in... if you want to try it out by yourself. This is still early beta material though!
#buildinpublic #rustlang #intar
Going to release the first beta version of the intar CLI tonight :)
#buildinpublic #rustlang
Auth is working + Cloudflare KV based allowlist. Aaaand Astro v6 beta ❤️
#buildinpublic
new year, new me. back to square 0. new auth based on better-auth and Astro + VM access via netbird. The platform will be awesome. The local CLI to run things is nearly done :)
#buildinpublic
Network is trickier because I want isolated networks for each group of VMs on one network device and one network device for SSH. The rest is easy. And resource allocation is hardcoded. Each VM has a CPU/mem and storage definition.
The first iteration of the local devops cli works (fix a broken nginx vm). Now I'm tuning the UI and later working on proper multi-vm setups (e.g. fixing broken k8s clusters)
#buildinpublic #intar
Planning a local-first single player version of the whole platform (which will be open sourced soon)
#intar #buildinpublic
Back on track
Going to post more progress tomorrow :)
#buildinpublic
I'll have to elaborate: docs.astro.build/en/guides/in... + vite dev server were super slow. There must be some magic toggle combo which would've saved me, but React is fine for now. I'll look into that when I have more time to focus on the frontend :) @svelte.dev is awesome
Did change my mind a bit and switched to ark-ui.com + @react.dev (Svelte compile times were just to slow)
#buildinpublic
Moving from @shadcn.com and @react.dev to ark-ui.com and @svelte.dev
#buildinpublic
Trying out github.com/github/spec-... rn to get better results with codex
#buildinpublic
Re-implemented atproto OAuth with www.better-auth.com and github.com/panva/oauth4...
Works like a charm :)
#buildinpublic
Next thing is VM creation
Figured it out, thanks to codex :)
Working on CI/CD for the website :)
intar admin interface showing a list of servers where a tooltip shows all sorts of OS info and hardware specs
Sweet. The agent now reports all sorts of server info (os, ram, cpu, ...)
#build-in-public #intar
intar logo. inspired by the Goa'uld 1 containing an energy crystal as a hint of an intar weapon
Inspired by the Goa'uld number 1, containing an intar energy crystal. I think I'll keep it, but will iterate on the glow of the energy crystal :)
a screenshot showing an admin ui for a tool called intar.dev (a devops training tool) - the selected view shows a list of servers
Nice, the agent connection is working in production :)
#build-in-public
