Will talk about Linux, plants, space, retro games, and anything else I find interesting.

Also mesa@piefed.social over on Piefed.

  • 186 Posts
  • 541 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle













  • It looks like it works VERY similar to magnet links. You get a link, you have a node that exists on the network that acts like P2P. Some interesting stuff on it.

    For those using Ubuntu/PopOS or any linux/mac distro:

    1. Go to the terminal and copy/paste curl -sSf https://radicle.xyz/install | sh (or remove the sh and check out the script yourself, it looked ok to me).
    2. Add in the new script within your bashrc. This may be different if your not using linux: source ~/.bashrc
    3. You should now have radicle installed. rad --version

    I was able to get this working after some new updates to the documentation made it much easier.

    You can use rad auth to make an identity. Afterwards you can see the details with rad self

    You can run a node here: rade node start. You may have to open up a port in order to get it working. I had to.

    Anyways it looks interesting. Im still trying to figure out where to get a list of repos/projects.

    I was able to pull down: rad clone rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5

    Has anyone used it before? Any specific repos that look interesting to you? This is my first time being actually successful bringing being successful to getting a repo.















  • Yep take a look, theres quite a few examples, but they use Github Actions, CircleCI, Gitlab etc… etc…

    Most CI/CD that use the above-ish model will use the same kinda scripts (bash or otherwise). Basically if you can do it on your desptop, you can automate it on a server. Make it work first, then try to make it better.

    Most of the time, ill throw my Docker/Docker Compose (and/or terraform if need be) on the root of the repo and do the same steps I do on the development side for building/testing on the CI side. Then switch over to CD with either a new machine (docker build/ compose) or throw it all on a new server. At that point, if you script it out correctly, it doesnt really matter what kind of server you use for CI/CD, since they are all linux boxes at the end of the day.

    You can also mix it up by using bare metal, docker alternatives, different password managers, QA tools, linters, etc…etc…

    But virtualization will get you quite far. In my opinion start with just trying to get the project to build on another server via a script from scratch, then transfer it over to the CI. Then go with testing/deployment.

    GL!