Forgjeo/Gitea support would be nice. I was waiting for Radicle for long but for our self hosting needs we are using Gitead then moved to Forgejo and never looking back.
Radicle 1.0 – A local-first, P2P alternative to GitHub
31–40 of 70 posts
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#32Related:
Radicle is an open source, peer-to-peer code collaboration stack built on Git - https://news.ycombinator.com/item?id=40166736 - April 2024 (53 comments)
Radicle: Peer-to-Peer Collaboration with Git - https://news.ycombinator.com/item?id=39868504 - March 2024 (10 comments)
How Radicle Works Under the Hood - https://news.ycombinator.com/item?id=39837117 - March 2024 (16 comments)
Radicle: Sovereign code forge built on Git hits v1.0 - https://news.ycombinator.com/item?id=39829736 - March 2024 (3 comments)
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative - https://news.ycombinator.com/item?id=39600810 - March 2024 (284 comments)
Understanding Peer-to-Peer Git Forges with Radicle - https://news.ycombinator.com/item?id=25322584 - Dec 2020 (14 comments)
Radicle: A peer-to-peer alternative to GitHub - https://news.ycombinator.com/item?id=25313010 - Dec 2020 (255 comments)
Radicle-Link: Extending Git with Peer-to-Peer Network Discovery - https://news.ycombinator.com/item?id=24382589 - Sept 2020 (37 comments)
Show HN: Radicle. A decentralized alternative to GitHub built on IPFS - https://news.ycombinator.com/item?id=19591011 - April 2019 (1 comment)
Radicle Architecture - https://news.ycombinator.com/item?id=19511525 - March 2019 (18 comments)
Radicle: A decentralized alternative to GitHub built on IPFS - https://news.ycombinator.com/item?id=19367916 - March 2019 (82 comments)
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#33> For this guide, we recommend installing Radicle under /usr/local. This will require you to have write permissions to /usr/local/bin and /usr/local/man. You can give yourself these permission by changing ownership of these directories to the current user and group: $ sudo chown $(whoami): /usr/local/{bin,man,man/man1} Seems kinda weird to chown all that in the install instructions? Or am I the weird one. Edit: This…
this is just horribly wrong
FYI the guide they're quoting is not for the usual installation but for hosting a seed box. Presumably the kind of thing you would spin up on a VPS and not use for anything else.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#34> For this guide, we recommend installing Radicle under /usr/local. This will require you to have write permissions to /usr/local/bin and /usr/local/man. You can give yourself these permission by changing ownership of these directories to the current user and group: $ sudo chown $(whoami): /usr/local/{bin,man,man/man1} Seems kinda weird to chown all that in the install instructions? Or am I the weird one. Edit: This…
this is just horribly wrong
Yeah, I wonder how much of the long-standing Unix philosophy & consistency is lost by breaking with best practices. autotools seems to be written off by many younger (and non- C) developers and maintainers, but still, it would be good to stick to consistent conventions on that platform.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#35These days when I collaborate with other developers, we do it all in a git repo that is simply hosted on a VM everyone has ssh access to. Project management is done in a plan/ directory which has task entries like 1000-add_logout_button.txt Where 1000 is the priority. There is also a directory plan/done/ where tasks go that have been completed. In the plan/done/ directory, the priority gets replaced by the completion…
That is a really cool system, thanks for sharing it! I've been looking for a text based way to do project management and this is giving me a bunch of ideas.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#36> The Radicle team is funded by Radworks. To date, around $7m has been granted towards the development of Radicle, by Radworks. That's quite impressive.
Some kind of crypto token is involved, bless them for doing something useful with the spoils.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#37Forgjeo/Gitea support would be nice. I was waiting for Radicle for long but for our self hosting needs we are using Gitead then moved to Forgejo and never looking back.
> Forgjeo/Gitea support
What exactly are you asking for here? A import/export tool to move all data between the two? AFAIK, both use Git already, so moving the actual code would be trivial and already possible.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#38Forgjeo/Gitea support would be nice. I was waiting for Radicle for long but for our self hosting needs we are using Gitead then moved to Forgejo and never looking back.
> Forgjeo/Gitea support What exactly are you asking for here? A import/export tool to move all data between the two? AFAIK, both use Git already, so moving the actual code would be trivial and already possible.
IMO: running a Foregjo instance would also export to the rad network.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#39This is a great idea and exactly what software development needs right now.
However there are a lot of things that seem more complicated than necessary.
https://radicle.xyz/guides/protocol
I'm reading through the delegate consensus model for branches and I don't see why any of that is necessary. It's encroaching on the P2P that Git already does well, which is who I decide to push and pull from. I think this project could learn a lot from the KeyBase model, which is to just be a transport for Git.
- Nodes in the network should host local Git remotes. In Git you would configure the remote (origin is the conventional default) to be the address of the local Radicle daemon + a public key for the device that owns it + the repository name. Something like `//repository_name" rel="nofollow">http://localhost://repository_name`. If the device_id is the local device then it stores the repository internally, otherwise it calls out to the P2P network.
- You can add multiple remotes to a Git repository, so you could have a remote for each copy of the repository on each Radicle device you care to sync with. Git push pull just works.
- You can use the very simple regexp branch protection model that GitHub and friends use on each device. e.g. master in MyRepo on DeviceA only allows pushes from DeviceB. DeviceIDs become the primitive for authentication. Groups of Device IDs become users.
- There is plenty of existing tooling for managing mirroring and syncing on top of Git. What we are missing is a way to securely push and pull between arbitrary devices on the network by cryptographic id. e.g. I'm on my laptop, I want to pull from new-feature4 on my friend's desktop, I know its public key, not its IP address, and I know the branch name, figure it out for me.
- This doesn't mean that the source of truth device has to be online to access the repository. Since there is a single source of truth it can sign any changes, and everyone interested can cache those changes, using the signature to know the refs are legitimate.
Re: Radicle 1.0 – A local-first, P2P alternative to GitHub
#40These days when I collaborate with other developers, we do it all in a git repo that is simply hosted on a VM everyone has ssh access to. Project management is done in a plan/ directory which has task entries like 1000-add_logout_button.txt Where 1000 is the priority. There is also a directory plan/done/ where tasks go that have been completed. In the plan/done/ directory, the priority gets replaced by the completion…
i love the simplicity. What do you do with team members who are terminal illiterate? Project manager/client?
The prophylactic effect of this could actually be a real benefit when the org is small.
As it grows, this type of as system will break down anyways :)