helpimnotdrowning.net (eternally unfinished)

  • 0 Posts
  • 5 Comments
Joined 2 years ago
Cake day: June 9th, 2023
  • helpimnotdrowning@lemmy.sdf.orgtoSelfhosted@lemmy.world•Design patternsEnglish
    0·
    7 months ago

    I’ve acknowledged that, while convenient, my (small) setup is still a burden that I would be asking someone to take. If your friends don’t already share your passion or knowledge for Linux/Docker/the intricacies of <whatever you may be running>, I doubt they’d be willing to take on what you leave them.

    My friends had a family member who had a giant setup of Raspberry Pi’s that did Pi-hole, Home Assistant, F@H, among many other services and machines (there were like 6 Pi s!). They passed some time ago, and there’s just no one in the family who was willing to take on the responsibility to learn how to manage everything that was going on—services have been slowly degrading/going down since then.

    Those who rely on your services will just go back to using Google Drive, watch-anime-free.org.ru, and pressing “Open LAN world” in the Minecraft client. I don’t think it’s okay, but if you’re out of the game, you won’t be there to object.

    That is to say, if you DO have friends that are knowing and willing, you need to leave plenty of good documentation. I haven’t been one to write much of anything, and I’ve already fucked up my shell profiles again because of no documentation, but I can give some general pointers:

    • What runs where?
    • Why are things configured in certain ways? (ie “$GameServer gets 4gb because going over creates GC stutters”, “$IP is blocked because of telemetry”, “$File is symlinked to /dev/null to effectively delete/override a rule from $SomewhereElse”)
    • List rules and their exceptions. (ie “Service ports are numbered this way because it looks nice”, “Except $Port because it conflicts with $SystemService”)
    • List things even if they’re from personal preference (ie “Service ports are numbered this way because it looks nice”, tells user that these are effectively meaningless and things shouldn’t break by changing these, barring common sense)

    Basically, leave meaningful comments that explain why something is the way that it is. You should be able to use this documentation yourself as reference material. Keep this documentation updated regularly, as frequently quoted “bad documentation is worse than no documentation” (or something like that)

    (sorry if this last section in particular doesn’t make much sense, I haven’t slept in $hours. feel free to ask for clarification!)

  • helpimnotdrowning@lemmy.sdf.orgtoLinux@lemmy.ml•Question: If windows is required, what distro do you recommend?
    0·
    7 months ago

    Office won’t run on Linux or through Wine (AFAIK), I’ve converted to using LibreOffice on both Linux and Windows, which has yet to give me any issues.

    Teams, as part of O365, also doesn’t have a Linux app, however… with the (paid) Thunderbird addon Owl for Exchange, you can read+send Outlook emails; it also adds a Teams icon to your Thunderbird sidebar that acts as a link to the web client.

    Thunderbird, by default, can only read from Exchange mailboxes, but can’t send from them. If you don’t want to pay, the developers are working to add full Exchange support as stock. (There are also less legitimate ways to get Exchange support, like cracking Owl, but out of respect for the addon dev, you’ll have to find it yourself)

    Edit:

    If you’re new to Linux as a whole, I’ve seen many recommendations for Mint (a Debian and Ubuntu derivative), but I’ve never tried it myself. I started with Debian since I wanted a stable system that wouldn’t break down by itself or something. It’s rock solid on my Framework 13 Ryzen.

    As for a Desktop Environment (DE), you can’t go wrong with GNOME or KDE. I prefer KDE since I don’t like the “look” of GNOME and it’s more “Windows-like” (but still it’s own thing), but it’s really just personal preference.