Has anyone got some experience/advice for choosing between the options? It seems like they are:

My usecase is just to have a local single instance for testing apps against. I prefer to spin stuff up in Docker on the homelab.

  • farcaller@fstab.shEnglish
    17·
    2 months ago

    Garage is trivial to get up and running and it’s more lightweight than minio nowadays.

    • Scrubbles@poptalk.scrubbles.techEnglish
      6·
      2 months ago

      That’s what annoyed me about minio. Started super crazy simple to set up, but I missed two updates and came back to AWS levels of mandatory configuration. Ffs I chose you because you were simple, not because I needed to replace s3

      • frizop@lemmy.worldEnglish
        2·
        2 months ago

        I went through this too, except I got pissed off and found a fips compliant image running the last version prior to their disk format changes. Gosh that royally pissed me off.

    • MangoPenguin@lemmy.blahaj.zoneEnglish
      5·
      2 months ago

      Garage definitely seems better suited for selfhosters and small setups, Minio is just so large and complex with specific requirements now.

  • conrad82@lemmy.worldEnglish
    4·
    2 months ago

    Which apps are you testing?

    I set up minio s3 for testing myself, but found that most of my docker services doesn’t really support it. So I went back to good old folders

    • thirdBreakfast@lemmy.worldOPEnglish
      2·
      2 months ago

      One I’m writing. I use the host file system (as I have a strong preference for simple) for it’s storage, but I’m interested in adding Litestream for replicating the database onto AWS.

  • rutrum@lm.paradisus.dayEnglish
    3·
    2 months ago

    I’ve used minio briefly, and I’ve never used any other self hosted object storage. In the context of spinning it up with docker, it’s pretty easy. The difficult part in my project was that I wanted some buckets predefined. The docker image doesn’t provide this functionality directly, so I had to spin up an adjacent container with the minio cli that would create the buckets automatically every time I spun up minio.

    But for your use case you would manage bucket creation manually, from the UI. It seems straight forward enough, and I don’t have complaints. I think it would work for your use case, but I can’t say its any worse or better than alternatives.

    • thirdBreakfast@lemmy.worldOPEnglish
      2·
      2 months ago

      Thanks, I ended up going with Garage, but it has the same issue. I assumed I could just specify some buckets with their keys in the docker-compose or garage.toml, but no - they had to be done through the api or command line.

  • Foster Hangdaan@lemmy.fosterhangdaan.comEnglish
    3·
    2 months ago

    If you need S3-compliant storage for testing and development, you can use an S3 mock server. I’ve tried the following for use in web development and CI environments, they are lightweight and configurable:

    There is also Localstack. I found this one to be a bit more complex than the ones above and ended up not sticking with it.

  • johntash@eviltoast.orgEnglish
    2·
    2 months ago

    Garage is the simplest of the three imo.

    I’ve only used it in a cluster, but it should be even simpler for one instance