• 1 Post
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle




  • Honestly the single biggest thing to self-hosting is breaking stuff.

    Host stuff that seems interesting to you, and dick around with it. If it breaks, read the logs and try to fix. If you can’t, revert to a backup and try to reproduce.

    If you start out with things that interest you, you’ll more likely stick with the hobby. From there you can move to hosting things with external access - maybe vpn inside your own network through your router?

    From there, get your security in line and host a basic webserver. Something small, low attack vector, and build on it. Then expand!

    Definitely recommend docker to start with - specifically docker compose. Read the documentation and mess around!

    First container I would host is portainer. General web admin/management panel for containers.

    Good luck :).








  • Hi. System Admin millennial here.

    You would think that’s the case, but in my experience it’s not.

    Millenials were around during a major shift/evolution in general home computer use, so we’re much closer to understanding the “flow” of tech, even if it’s older. Gen-Z tries to think in smartphone or tablet mode.

    Younger Gen-Z are the same as a blue collar boomer: when the company I work for hires a Gen-Z employee, I spend a ton of time with them the first few weeks “fixing” their “broken” machines. Most of the Millenials that are hired can do the general troubleshooting themselves.

    I will agree with the music bit though.