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.

@Moonrise2473@feddit.it
link
fedilink
English
72M

I set garage via docker and it was not impossibly hard.

Main problem is that there isn’t an admin panel and you can’t login to the docker container via docker exec, so you have to write some python (or other language of your choice) to send requests to the API port to:

  1. Set the layout of your server
  2. Create an user
  3. Create a bucket
  4. Assign that bucket to your user
@thirdBreakfast@lemmy.world
creator
link
fedilink
English
22M

Thanks. I ended up going with Garage (in Docker), and installed the minio client cli for these tasks.

@palitu@aussie.zone
link
fedilink
English
32M

Postman is great for sending api queries.

@johntash@eviltoast.org
link
fedilink
English
32M

You can use docker exec with garage docker image.

I’m on mobile but I think you just need something like: docker exec containerid ./garage stats

@Moonrise2473@feddit.it
link
fedilink
English
22M

Ah maybe I was missing the ./ , it said garage not found on path (on mobile, can’t try)

@thirdBreakfast@lemmy.world
creator
link
fedilink
English
32M

This is correct, I already installed the minio cli, but when I came back and read this, I tried it out and yes, once garage is running in the container, you can

alias garage="docker exec -ti <container name> /garage"

so you can do the cli things like garage bucket info test-bucket or whatever. The --help for the garage command is pretty great, which is good since they don’t write it up much in the docs.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 124 users / day
  • 419 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog