hyperrealI'm currently trying to wrap my head around setting up Radicle. The decentralization is kind of confusing when I'm used to centralized git hosting.
I have a selective seed node on my public-facing server, along with the radicle-httpd service which is reverse-proxied via Caddy. As I understand, this means I can seed (replicate) selected public repos to keep them in sync with the network. And the radicle-httpd service makes them available in an HTTP JSON API(?).
I also have a regular node on my workstation, with my dotfiles repository added to it for testing purposes.
I'm not sure how a regular node differs from a seed node. Do regular nodes also seed repositories like a seed node does, while a seed node's purpose is solely for seeding? If regular nodes also seed, is there still any reason to run a seed node separately?
I'd also like to get the radicle-explorer web UI set up on my public-facing server via reverse proxy. I'm not sure how that fits in with the rest of this. Does the radicle-explorer have to point to my seed node's HTTP endpoint to display the repositories I'm seeding?
I might have to go bother people in the Zullip chat.
Nic Roland 