You may have noticed a few of my posts here, I am very interested in self-hosting and what advice can you give to a newbie? maybe some literature, video, I don’t know~

  • tburkhol@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 months ago

    Ditto. Started 20 years ago with one service I wanted. Complicated it a little more every time some new use case or interesting trinket came up, and now it’s the most complicated network in the neighborhood. Weekend projects once a year add up.

    If you have the resources, experiment with new services on a completely different server than everything else. The testing-production model exists for a reason: backups are good, but restoring everything is a pain in the ass.

    I also like to keep a text editor open and paste everything I’m doing, as I do it, into that window. Clean it up a little, and you’ve got documentation for when you eventually have to change/fix it.

    • Hominine@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      10 months ago

      I also like to keep a text editor open and paste everything I’m doing, as I do it, into that window. Clean it up a little, and you’ve got documentation for when you eventually have to change/fix it.

      Smart stuff that is leaving me feeling dumb for not having thought of it myself, shell history is a poor substitute.

      • anamethatisnt@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        10 months ago

        For linux this is as easy as script <filename>, ex:
        [user@fedoragaming ~]$ script 20240313InstallingJellyfin.log
        Script started, output log file is ‘20240313InstallingJellyfin.log’.
        [user@fedoragaming ~]$ exit
        exit
        Script done.

        edit: and for Windows I recommend using putty, it can also save sessions to logs.