Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Im doing something very similar. Running my OpenCode on a proxmox lxc. I have an additional layer of Kimaki, which gives you Discord integration (hate it or love it). Chatting with your codebase (voice messages, too, if that’s your jam), is very very cool.by dlxfoo
- > I set up OpenCode Web UI with Git access to make my homelab easier to manage. OpenCode pushes to Git, I approve the PRs, GitOps deploys the changes. Best of all, OpenCode runs as a server with persistent coding sessions synced across devices.
> I’ll share my homelab setup soon. There are about a dozen docker compose stacks for the services that I manage.
That is probably neat, but before I read, how many thousands of dollars would I need to spend to acquire the RAM and GPUs needed to do something similar?
by palmotea - I’ve been building something similar for quite a while, with a stronger focus on minimizing dependencies on external services: https://github.com/kvladsrc/gym/tree/main/production
I find it convenient to interact with frontier LLMs through a Kanban board powered by Kanboard. For example, the LLM creates backlog tasks based on alerts from the cluster. I manually move selected tasks from the backlog to Ready, the model picks them up, works on them, and submits a patch for review in the comments. From there, the usual pipeline takes over: CI, LGTM, merge, and CD.
Another surprisingly useful part is desktop configuration management, covering everything from the compositor and system tray to text editor configuration with the same pipeline. For once, I genuinely enjoy using Linux on the desktop.
by zjgkknk - Any idea as of why this domain is blocked by quad9 resolvers? I am unable to open the website because Quad9 filters the domain:
dig @9.9.9.9 rsgm.dev NS
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; EDE: 17 (Filtered)by schanz - I've added a few more bells and whistles to my agentic rube goldberg, but the gist is forgejo tag listeners triggering argo workflows to orchestrate
1. issue tag
2. write pr
3. testing
4. review+revise loop
5. merge mutex to ensure you don't get a merge storm
6. rebase and merge
I've been trying really hard to have it properly implement agentic identity where the pod gets a spiffe-attested token and then trades that for access to the vault secret for a project-scoped forgejo service account. I wish forgejo could configure a trusted external jwt signing authority so I could skip vault and the accounts.
Here's the inspiration for the auth model I've been trying to implement: https://datatracker.ietf.org/doc/draft-klrc-aiagent-auth/
The last piece has been using gvisor + kubernetes agent sandboxes. My fable adventure last week was having it debug the process of attesting and distributing workload identities for agents running in gvisor, as it creates a layer of indirection that confuses spire to the point it won't issue an ID.
by constGard - I've been trying to find the motivation to do a write up on my AI lab, and this is just what I needed. Thanks for sharing. My setup is a similar idea, just with n8n/git/argo/k3s. It's mainly for automated workflows that Qwen or Gemma4 can handle.by doctorspazz
- Some times I feel like a lot of people in tech independently go through the same things right around the same time with few people writing/sharing about it.
I am also creating this and enjoyed the post and comments all going through the same thing :)
by MisterPea - I've been doing something pretty similar, except instead of having a persistent opencode server, I've been using this workflow that runs opencode inside of the Forgejo action runners:
https://codeberg.org/dragonfyre13/forgejo-opencode
Still tinkering with it, but the gist is that I can invoke Opencode with /oc inside of an Forgejo issue, then it will come back with a PR for me to review.