Comment on 18% of people running Nextcloud don't know what database they are using

• stardreamer@lemmy.blahaj.zone ⁨1⁩ ⁨month⁩ ago

  Exactly. Unless you are actively doing maintenance, there is no need to remember what DB you are using. It took me 3 minutes just to remember my nextcloud setup since it’s fully automated.

  It’s the whole point of using tiered services. Do you also worry about your wifi link-level retransmissions when you are running curl?

  source

  • IncogCyberspaceUser@lemmy.world ⁨1⁩ ⁨month⁩ ago

    Sorry for the newbie question, but how is your nextcloud setup automated? Is that like a compose/yaml file?

    source

    • stardreamer@lemmy.blahaj.zone ⁨1⁩ ⁨month⁩ ago

      stares at 300 line shell script+ansible mess that updates/sets up Forgejo, Nextcloud, ghostcms

      “Yes… It’s automated”

      source
• u_tamtam@programming.dev ⁨1⁩ ⁨month⁩ ago

  Self hosting doesn’t mean “being wasteful and letting containers duplicate services”. I want to know which DB application X is using, so I pool it for applications Y and Z.

  source

  • Ajen@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

    For most applications the overhead of running a second DB server is negligible.

    source

    • absentbird@lemmy.world ⁨1⁩ ⁨month⁩ ago

      And if it’s SQLite (which I believe is the default) it’s really just reading and writing a file on the file system.

      source
    • u_tamtam@programming.dev ⁨1⁩ ⁨month⁩ ago

      I disagree. You are just entertaining the idea that servers must always and forever be oversized, that’s the definition of wasteful (and environmentally irresponsible). Unless you are firing-up and throwing-away services constantly, nothing justifies this and sparing the relatively low effort it is to deploy your infrastructure knowingly.

      source

      • Ajen@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

        Do you have the data to back that up? Have you measured how much of an impact on system load and power consumption having 2 separate DB processes has?

        Roughly the same amount of work is being done by the CPU if you split your DBs between 2 servers or just use one. There might be a slight increase in memory usage, but that would only matter in a few niche applications and wouldn’t affect environmental impact.

        source

        • -> View More Comments
  • tburkhol@lemmy.world ⁨1⁩ ⁨month⁩ ago

    This is one of my pet peeves with containerized services, like why would I want to run three or four instances of mariadb? I get it, from the perspective of the packagers, who want a ‘just works’ solution to distribute, but if I’m trying to run simple services on a 4 GB RPi or a 2 GB VPS, then replicating dbs makes a difference. It took a while, but I did, eventually, get those dockers configured to use a single db backend, but I feel like that completely negated the ‘easy to set up and maintain’ rationale for containers.

    source

    • u_tamtam@programming.dev ⁨1⁩ ⁨month⁩ ago

      Precisely what pre-devops sysadmins were saying when containers were becoming trendy. You are just pushing the complexity elsewhere, and creating novel classes of problems for yourself (keeping your BoM in control and minimal is one of many others that got thrown away)

      source