Hacker News new | ask | show | jobs
by xvilka 32 days ago
I wish they would make local-only deployment easier. For example, lets take 3 machines and try to setup Radicle to work only on those, without joining the common Radicle network. Like on-premises GitLab, but decentralized, without the need of the server. It requires quite some serious scripting and usecase not covered in the documentation.
4 comments
endiangroup 32 days ago
AD: We've just been discussing this! There's an open RIP [^1] that we will be supplying feedback for soon.

[^1]: https://radicle.zulipchat.com/#narrow/channel/369876-RIPs/to...

link
survirtual 30 days ago
I patched my local radicle to remove the default seeds, and I can put my own seeds as default. It is pretty easy to script some commands that auto add your local nodes when init a repo.

I also added some network rules to block non-local network access to radicle. Not needed but I really wanted it to work only on my lan.

Works great. I setup several skills for agent harnesses and they use radicle + jj + git perfectly. It is fun watching issues pop up and monitoring progress via the flow.

I am building more tools around this workflow because it is so effective. Radicle acts as the long term project memory bank and management. I can write issues and they can automatically be picked up.

What I'm adding is making the issues more searchable and an agent proxy that integrates radicle into calls. among other things.

This is all pretty straight forward to do, I really recommend it.

link
vanous 32 days ago
Same here... I have been looking at all the self hosting options for a while but swapping one centralized system for another isn't what I would prefer. Running/using local and community gitea/forgejo has been good, but I hope decentralized radicle could be the solution to more independence.
link
heresie-dabord 32 days ago
A containerised deployment would (understatement warning!) be useful.
link
gsaslis 32 days ago
This is a good fit primarily if you want to run a Radicle node that only seeds repos you tell it to. If you want to write code which you publish on Radicle, you need the tool that signs all your work with your private key (of your Radicle identity) - i.e. the `rad` CLI - and running that in a container isn't very useful. (e.g. think about how you'd replace `rad clone`). Having said that, here's a container image I maintain, in case it helps: https://quay.io/repository/radicle_garden/radicle-node
link