Sometimes I'm supposed to be working on bad servers, but I'm actually remoted home working on good servers.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
The day I added the keys to my home server on my work machine was the day my productivity plummeted
I wouldn't want to do that, I don't trust bad computer enough to work on good computer with bad computer
I had total control over my bad computer. It was more like that friend you like but who makes you do bad stuff occasionally
Same for me luckily, but I just don't like the idea that my work laptop has access to private stuff. For example, I made a second account for my git Server for my work laptop.
you haven't seen the state of my server have you
It can't be worse than an outdated public facing Windows server, right?
That's a big oof
The worst thing is when everything is airgapped. Tasks that take 5 minutes at home end up taking a week because there's always something not being available or whatsoever.
And then sometimes you use a work server to design the pattern for the home server.
Speak for yourself, I did the opposite, use my home patterns to fix stuff at work.
The magic of the bad server is they have an R&D budget plus ops team so some waste while testing is covered, you tend to pay for mistakes on the good (home) server :P
Plus getting feedback from a good team beats a rubber duck XD
My office's IT helpdesk guy had a similar comic in his office. 3 panels of a guy at his work computer miserable, and the last panel he's at home on his own computer happy as a clam. So true
This is way too accurate. With a buddy I even have what our wifes call playdates, where we are messing around with proxmox, containers and linux distros. We both have some old poweredge servers, laptops, raspberry pies and old phones to mess around with. Nothing useful has come out of that so far, although we're preparing a lemmy and mastodon instance, so we're getting there.
I'd expect the work servers to be better because I can't afford to spend thousands per server, but maybe I'm just spoiled with regards to work hardware.
It's not about the server being strong or weak. Good server is the one you associate with your own projects and hobby, bad server is the one you associate with work and oblications :-)
True, that's fair.
For a while I was doing the work from home thing, and I found it hilarious that I'd be sitting in the same chair and it'd be like "CLOSE THE LAPTOP OF WORK! OPEN THE LAPTOP OF PLAY!"
We got separated from the main frame at work. And got full control for our own servers. Don't ask why our system runs 100% uptime without errors.
If only I was in charge, everything would be perfect. Why can't those morons get it right?
Fuck yeah, punish me