398
This is the back of my 10" Mini server rack -- Custom made 3D printed power modules for each server (thelemmy.club)
submitted 11 hours ago* (last edited 11 hours ago) by to c/selfhosted@lemmy.world
44 comments fedilink hide all child comments
 

I've seen so many 10" servers that look amazing from the front and very polished, but then having a rats nest of cables and a mess at the back.

After 62 iterations and many 3D prints, blood, sweat, profanity and tears. I my design and implementation is finally done. image
I used Hexagons where possible, because as you know, Hexagons are the bestagons

This is Before:
image

And the After:
image
The ducky adds 200MHz

The front of my mini-rack is actually still somewhat of a mess, I thought I'd focus on the back first.

I've published it in excruciating detail on my GitHub Leave a Star if you like what you see.

I self host a bunch of stuff on here to get away from Big-Tech, and because I find it fun. For a lot more details see https://erasmus.works/

It always bothered me the the fronts of racs are modular, but not the backs, this solves that
If you have any questions feel free to ask, hopefully this helps other clear up their rats nests.

you are viewing a single comment's thread
view the rest of the comments
[–] 19 points 8 hours ago (5 children)

I totally get that

Quick heads up - codeberg has an option to auto push changes to github, or the other way around with a github action (I prefer codeberg first)

May want to give it a try, from a client perspective you can also use that to note that a distributed approach provides resiliency (and now it becomes a selling point too)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 9 points 8 hours ago (2 children)

    Nice thanks, that sounds good. I'd definitely only want to push to one place, if it then syncs to GitHub that's fine.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 8 hours ago (1 child)

    I'm with you, I don't like having to do the same thing more than once

    I set up an "about my repos" repo, which has a readme detailing the process, and explanations of what is where and what they are all for, which is what I point clients to. That also has a link to my personal forgejo to demo local git as well (which can also sync, btw) along with a note that it may be down for various reasons like updates or changes I'm making, which is why I also sync elsewhere.

    Depending on what services you're selling to clients, it makes for a neat and simple addition to the list of skills to demo!

    And you're kind of making me want to use a mini rack as an excuse to my wife for a 3d printer, but she already knows I'm not getting rid of my 12-15RU racks under my desks, so I'm going to have to wait until we find the property we want so I can build my workshop....

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 7 hours ago (1 child)

    It seems that using multiple remotes is also possible. So instead of syncing two repos, push to both at once.

    https://git-scm.com/docs/git-remote#Documentation/git-remote.txt-set-url

    https://stackoverflow.com/questions/849308/how-can-i-pull-push-from-multiple-remote-locations/12795747#12795747

    git remote set-url origin --push --add user1@repo1
git remote set-url origin --push --add user2@repo2
git remote -v
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 7 hours ago*

    You can, but you can also run into some issues if you have git LFS, if one rejects for whatever reason, or sometimes just branch issues.

    Thats why I prefer to go to one repo and push out from there, but it is absolutely doable with git by itself.

  • permalink
  • fedilink
  • source
  • parent