• geography082@lemm.ee
    link
    fedilink
    English
    arrow-up
    4
    ·
    7 hours ago

    Now explain this to EU based corporations, which in my opinion needs to be the focus on making the change. They drive the economy. All major assets in software income are being routed to American firms through their licenses.

  • utopiah@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    13 hours ago

    Nice, DINUM is doing a lot so great to see go beyond with supra national collaboration!

    I’m using NextCloud (Germany and international open source community) hosted on Webo (Slovenia) with data centers in Germany and Helsinki (so I bet on Hetzner). I’m happy with it but I’ll keep on eye on https://github.com/suitenumerique/docs

    • utopiah@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      13 hours ago

      I’d be curious, they use Minio which puts S3 first. Does it mean Docs (the official instance) is relying on AWS?

      If so IMHO that’s not a great default EU sovereignty.

      • hoppolito@mander.xyz
        link
        fedilink
        English
        arrow-up
        3
        ·
        12 hours ago

        I would assume (without having looked at the codebase) that if they use minio they are, by default, not reliant on AWS.

        Minio is its own S3 implementation which can be self-hosted.

        S3, being an AWS protocol originally has AWS environment variables all over the place but that does not necessarily mean a reliance on the service. Rather, they rely on the protocol and you bring your own S3 endpoint I would assume. be that minio, hetzner or what have you.

        • cmhe@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          12 hours ago

          I thought that MinIO is a Open-Source S3 implementation, which you can just install on your own system. S3 is a “protocol” here IIUC.

          Is your complaint that they are using the S3 protocol, because it was invented and is controlled by AWS?

          Or that some services might use it without MinIO, directly on AWS?

          • utopiah@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            12 hours ago

            Seems I misunderstood, if it’s solely the branding (of that implementation) then it’s fine. I thought they relied on AWS itself.

  • AnonomousWolf@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    14 hours ago

    We already have kDrive you get 1TB storage for only 2€ a month, it’s based in Switzerland

  • stoly@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    22 hours ago

    Really cool. I tried to sign up but you have to be part of an officially recognized organization in France and input their registration number as part of the process.

      • stoly@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        I’m sure it will be. This is a government funded thing in the early stages so I can see how they would set it up that way.

    • meliaesc@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      21 hours ago

      I definitely don’t want the government attached to my personal files, in any country.

  • شاهد على إبادة@lemm.ee
    link
    fedilink
    English
    arrow-up
    45
    arrow-down
    3
    ·
    1 day ago

    Calligra and LibreOffice already exist though. I am not against this in principle but couldn’t they have invested in an existing FOSS project?

  • genomebandit@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    ·
    1 day ago

    Really glad to see the EU adopt more open source software as a way to combat the centralized control some of the american software companies have over the space.

  • flop_leash_973@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    ·
    edit-2
    1 day ago

    As someone in and from the US, good. Private companies are far to prevalent in public institutions all over the world. Something as basic and fundamental as word processing should not be controlled by a small select few huge international companies.

  • cley_faye@lemmy.world
    link
    fedilink
    English
    arrow-up
    111
    arrow-down
    2
    ·
    2 days ago

    Just checked the part about self-hosting. While it’s probably possible to handle things with a less heavy approach, their only “easy to use” example right now is to have a full-blown kubernetes cluster at hand or run locally in the source directory. That’s a bit much.

    • NekuSoul@lemmy.nekusoul.de
      link
      fedilink
      English
      arrow-up
      38
      ·
      edit-2
      2 days ago

      In the README there’s also instructions for Docker Compose, although it’s quite the compose file, with SIXTEEN containers defined. Not something I’d want to self-host.

      • lostbit@feddit.nl
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        1 day ago

        it seems to contains development containers and external services containers. So the compose file is more for local dev it seems

        What i do find weird is the choice for Django for the backend. Python is incredibly slow, and django rest framework is even worse.

    • Lodra@programming.dev
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      3
      ·
      2 days ago

      Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios

      • cley_faye@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        ·
        2 days ago

        I don’t like the approach of piling more things on top of even more things to achieve the same goal as the base, frankly speaking. A “local” kubernetes cluster serve no purpose other than incredible complexity for little to no gain over a mere docker-compose. And a small cluster would work equally well with docker swarm.

        A service, even made of multiple parts, should always be described that way. It’s easy to move “up” the stack of complexity, if you so desire. Having “have a k8s cluster with helm” working as the base requirement sounds insane to me.

        • mac@lemm.ee
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          1 day ago

          Honestly, a lot of the time I don’t understand why a lot of businesses use k8s.

          At my company especially, we know almost exactly what our traffic will look like from 9am-5pm. We don’t really need flexible scaling, yet we still use it because the technology is hyped. Similar to cloud, we certainly don’t need to be spending as much as we do, but since everyone else is on or migrating to the cloud, we are as well.

          • azertyfun@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 hours ago

            The “problem” with k8s is not that it’s abstract-y (it’s not inherently any more abstract than docker), it’s that it’s very complex and enterprise-y.

            The need for such a complex orchestration layer is not necessarily immediately obvious, until you’ve worked on a complex infra setup that wasn’t deployed with kubernetes. Believe me when you’ve seen the depths of hell that are hundreds of separately configured customer setups using thousands of lines of ansible playbooks, all using ad-hoc systems for creating containers/VMs, with even more ad-hoc and hacked together development and staging environments, suddenly k8s starts looking very appetizing. Instead of an abominable spaghetti of bash scripts, playbooks, and random documentation, one common (albeit complex) set of tools understood by every professional which manages your application deployment & configuration, redundancy, software upgrades, firewall configs, etc.

            A small self-hosted production kubernetes cluster doesn’t have to be hard to operate or significantly more expensive than bare-metal; you can buy 3U of rack space, plop in 3 semi-large servers (think 128 GB plus a few TB of SSD RAID), install rancher and longhorn, and now you’ve got a prod cluster large enough for nearly every workload such that if you ever need to upgrade that means you have so many customers that hiring a k8s administrator will be a no-brainer.

            Or you can buy minutes from AWS because CapEx is the absolute devil and instead you pay several times as much in OpEx to make it someone else’s problem. But if you’re doing that then you’re not comparing against “installing things the old-fashioned way”.

            • mac@lemm.ee
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 hours ago

              Thanks for the response!

              I personally haven’t rolled a k8s or k3s cluster, so it’s always felt a bit abstract to me. I probably should though, to demystify it to myself in my work environment.

              Complex is definitely what I have noticed when I see my devops team PR into the ingress directories.

              I guess the abstract issue I see, that ties in to the meme i shared above, is that sometimes around deploys where we get blips of 503/4’s and we appear to be unable to track them down. Is it the load balancer? Ingress? Kong? The fact that there is so many layers make infra issues rough to debug

          • loudwhisper@infosec.pub
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            Kubernetes is not really meant primarily for scaling. Even kubernetes clusters require autoscaling groups on nodes to support it, for example, or horizontal pod autoscalers, but they are minor features.

            The benefits are pooling computing resources and creating effectively a private cloud. Easy replication of applications in case of hardware failure. Single language to deploy applications, network controls, etc.

        • Lodra@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 day ago

          Yea I’m not a fan of helm either. In fact, I avoid charts when possible. But kustomize is great.

          I feel the same way about docker compose. If it wasn’t already obvious, I’m biased in favor of k8s. I like and prefer that interface. But that’s just preference. If you like docker compose, great!

          There’s one point where I do disagree however. There are scenarios where a local k8s cluster has a good and clear purpose. If your production environment runs on k8s, then it’s best to mirror that locally as much as possible. In fact, there are many apps that even require a k8s api to run. Plus, being able to destroy and rebuild your entire k8s cluster in 30s is wonderful for local testing.

          Edit: typos

          • cley_faye@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            I won’t argue with the ups and downs of each technos, but I recently looked into docker swarms and it was all I expected kubernetes to be, without the hassle. And I could also get a full cluster with services restored from scratch in 30s. But I am obviously biased towards it, too :)

            • Cpo@lemm.ee
              link
              fedilink
              English
              arrow-up
              1
              ·
              8 hours ago

              Did not realize swarm was still a thing, not trying to be offensive here.

              My best find was using traefik as a reverse proxy in docker (compose). It is easily configurable through container labels and pulls resource definitions straight from docker. It is awesome!

      • lostbit@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        k8s is overkill for a lot of homelabs. Using docker compose is a fraction of that complexity

        • Lodra@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          23 hours ago

          There are many reasons to use k8s. Managing multiple nodes is one good one. But more importantly, k8s gives you an api-driven runtime environment. It’s really not comparable to docker compose.

      • Metju@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        Seconding k3d (and, by extension, k3s). If you’re in a market for sth suitable for more upstream-compliant clustering solution (k3s uses SQLite instead of etcd, iirc), RKE2 is also a great choice

    • Tramort@programming.dev
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      2 days ago

      Please develop this self hosted version using sandstorm

      It makes hosting a breeze with one click installation

        • kerrigan778@lemmy.world
          link
          fedilink
          English
          arrow-up
          32
          ·
          1 day ago

          I was going to make a joke but honestly it’s refreshing and a good sign that Lemmy is starting to get used by people who don’t know what FOSS means now. Welcome.

        • Allero@lemmy.today
          link
          fedilink
          English
          arrow-up
          19
          ·
          edit-2
          1 day ago

          Nice to see Lemmy is not just a place for complete nerds!

          FOSS is free and open-source software. In simple terms, it is any program for which the source code (i.e. the actual code that forms the program, its entire backbone) is available for anyone to see and modify as they see fit, without any technical or legal limitations.

          This is normally seen as very positive, because everyone with the knowledge of respective programming languages can inspect the program to see it doesn’t do anything malicious, and everyone can change the program to their needs. Also, the original creator of the program does not have power to put any limitations on its use, like introducing payment requirements, or deleting important features, because everyone can immediately spawn a version of the program that doesn’t have these changes, while still having the rest.

          • Queen HawlSera@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            14 hours ago

            So… how do I use it? I tried signing up on the site, but… it said something about an organization it was poorly transltaed from French to English, so I couldn’t tell what I was doing… I got as far as registering my current email address

            • Railcar8095@lemm.ee
              link
              fedilink
              English
              arrow-up
              3
              ·
              13 hours ago

              It might be a bit early for you. It’s in a way like Lemmy, somebody has to put it on a server and let you use it.

              It’s meant for government agencies to deploy and use (although anybody with some self hosting knowledge can do on their servers, including hobbiests and companies)