Apologies for the poor grammar, English IS my first language and so I’m rather flagrant with runons.

I’m really not half as tech literate as half the people on the fediverse, but my noia about the state of online cloud hosting and lack of control over my data has led me far out of my depth. I’m wanting to set up a LibreCMC router and connect it to some type of home server (made of local office E-Waste) for media storage, email hosting, and fucking Minecraft servers or something. I promise I’ve tried my best in searching for the problem but often find myself floundering in 3-letter acronyms, and relations between systems I don’t understand (like dockers, or the Jellyfin vs Plex argument.) I don’t need an explanation but maybe some orientation on where I am to look for resources on these topics that assume I’m the 6 celled neurobase I am.

Thank you for your help, or your chastising.

Edit: thank you everyone for your replies! I’ll hopefully keep you all updated as I work through learning Linux terminals, and destroying terabytes of data in horribly predictable mistakes : )

  • klangcola@reddthat.comEnglish
    3·
    13 hours ago

    I had never heard of dockge before, but this sounds like the killer feature for me:

    File based structure - Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands

    Does that mean I can just point it at my existing docker compose files?
    My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.
    I have portainer, but rarely use it , and won’t let it manage the configuration, because that interfered with versioning the config in git.

    • Seefoo@lemmy.worldEnglish
      1·
      8 hours ago

      I tried out Komodo, but gave up on it. I looked at dockge after, but opted not to try it out. I prefer the IaaC setup with my compose in a repo for versioning and rollback. And while I think you can probably combine the two, komodo was getting in the way most of the time. It centered around secrets management and generating those secrets at run time.

      That said, I feel like if I expand beyond a single server I may go back to one of these tools

    • myrmidex@belgae.socialEnglish
      1·
      13 hours ago

      Does that mean I can just point it at my existing docker compose files?

      You add the compose via the DockGE UI, it then creates the necessary files and folders in /opt/stacks/. Not sure whether it works the other way around: to create the folder, copy the compose file in there, and see if it is recognized.

      I’ve been using it for over a year, works very smooth.

      • klangcola@reddthat.comEnglish
        2·
        13 hours ago

        Do you version your compose files in git? If so, how does that work with the dockGE workflow?

        • myrmidex@belgae.socialEnglish
          1·
          12 hours ago

          No, I don’t, I only back up /opt/stacks to borgbase. I imagine it should be possible, but it might depend on how the projects are arranged in git. Monorepo might give trouble, but separate repo’s might work.