Next evolution, just a one line bash script.

  • rushaction@programming.dev
    link
    fedilink
    arrow-up
    32
    arrow-down
    1
    ·
    5 months ago

    For me it’s more like new interesting self hosted project and then find out it’s only distributed as a docker container without any proper packaging. As someone who runs FreeBSD, this is a frustration I’ve run into with quite a number of projects.

    • zaphod@lemmy.ca
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      1
      ·
      edit-2
      5 months ago

      Eh even as a Linux admin, I prefer hand installs I understand over mysterious docker black boxes that ship god knows what.

      Sure, if I’m trialing something to see if it’s worth my time, I’ll spin up a container. But once it’s time to actually deploy it, I do it by hand.

      • JasonDJ@lemmy.zip
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        5 months ago

        If it’s an open-source project, usually the dockerfiles are available for reading.

        Do you audit every line of code that you run in production? If you are trying some new python/django/sql app, are you reviewing all that?

        I’d assume with a python based project, you’d be able to at least look at requirements and tell there’s something that sets off red flags. And you are either familiar/trust the maintainer, or you are reviewing the actual python itself?

        Beyond that, the dockerfile is essentially just installation instructions for getting it running on a virgin system of X distribution. I wouldn’t call that a black box.

        If the container isn’t part of an open source project, then this is a moot point then. The project itself is a black box.

        • zaphod@lemmy.ca
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          5 months ago

          You do you. Speaking for myself, I prefer to understand and be able to trivially inspect and modify the moving parts in the things I deploy so I have a snowball’s chance in hell of debugging and fixing things when something inevitably goes wrong.

            • zaphod@lemmy.ca
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 months ago

              And all I see is someone taking this conversation way too personally.

              • JasonDJ@lemmy.zip
                link
                fedilink
                arrow-up
                1
                arrow-down
                3
                ·
                5 months ago

                You sound like someone who doesn’t want to save 10 minutes of work every day because it might cost you half an hour every month.

      • rushaction@programming.dev
        link
        fedilink
        arrow-up
        7
        ·
        5 months ago

        Virtualization in general? Sure, I can. I’ve tried it a bit with bhyve. But it’s definitely a lot heavier since I’m now running a full Linux os and dedicating resources to it to run docker just to run a python or node app.

        Learning the project is in Go though is a sigh of relief. Professionally I’ve moved to Go (from Python) just because it’s so damn easy to build and distribute.

        I just wish there was better support for the other *nix’s. While the language support them just fine, docker on the other hand strangles it. =(