• 0 Posts
  • 15 Comments
Joined 5 years ago
cake
Cake day: January 29th, 2021

help-circle








  • I’ve just migrated most of my repos from Codeberg to Sourcehut (sr.ht) and I really like it. I’ve got nothing against Codeberg or Forgejo, they’re awesome, but I just really like the simple design of Sourcehut.

    The git send-email workflow was new to me, but I started liking it fast! I’ve never really enjoyed the web-based MR/PR workflow of GitHub anyway (read: it feels very slow).

    Sourcehuts CI system if also really nice overall, although there are some things I miss from the great CI that GitLab has. Mostly I miss only running pipelines when tags are pushed, and stuff like that.




  • I’ve been running my homelab on GMKTec something for around one and a half year now, with a bunch of HDD’s and an SSD connected via USB. The HDD enclosure is some cheap thing from Amazon, but I’ve never had a problem with it. Does the enclosure you’re trying to use have dedicated power? Or are you powering the SSD’s via the USB ports? That’s the only thing I can think of that would potentially be a problem.



  • Maybe because it’s not an obviously wanted feature? But I’m just guessing. You should request it and see what happens, maybe more people want it. I’ve never even thought about it, since in the case of Podman/docker it’s so “obvious” and easy to just mount network shares to the host first. And in the case of Kubernetes you can just mount NFS shares directly into pods.


  • I definitely do not hate SELinux, I think it’s a great system. But my experience mostly (at home, anyway) comes from managing servers running Kubernetes clusters and, like, just using podman do deploy containers. In both these cases SELinux is a on “just works” basis, for the most part.

    Then in enterprise environment that doesn’t run everything on containers, you usually have a very standardized way of applying SELinux policies. At my last place of work we did it via a rather Ansible role. It was simple and easy.

    But I can imagine using SELinux at home, where you maybe don’t have these things, might be a rather “mysterious” experience. It’s not the most obvious system.

    But learning to write your own policies (even if just trough se2allow or whatever it’s called) does de-mystify SELinix pretty quick.