Ente CommunityEC
Ente Community•4d ago•
15 replies
/dev/cy

Ente Self-hosting with Garage

Following the Garage docs for Ente and I'm at this section:
export CORS='{"CORSRules":[{"AllowedHeaders":["*"],"AllowedMethods":["GET", "PUT", "POST", "DELETE"],"AllowedOrigins":["*"], "ExposeHeaders":["ETag"]}]}'
aws s3api put-bucket-cors --bucket ente --cors-configuration $CORS

I'm confused about...

- is it okay to just... * the AllowedOrigins on a publicly exposed endpoint? or should I remove the port mappings in the compose file so Ente connects with Garage within the virtual network defined in compose?
- for context, i have all the Ente/Garage services on a compose network called ente
- how does the aws CLI interact with Garage? ig it's more of a Garage question than Ente, but I assume people who have set up Ente with Garage would know. i tried running the above command and it errors saying i need to run aws login. but that gives me an AWS login URL (ofc, as expected). not sure how that is relevant in a self-hosting scenario... i want everything running locally on my homelab
- except for the above aws CORS step I did everything else, and i was able to get Ente server and web, as well as postgres running, and was able to access the web version, and add the API to my iOS app. but when adding photo to Ente, upload fails and shows a lot of CORS errors in the console logs on the webapp

More context

- config available here: https://github.com/cybardev/homelab (with Ente activated while I try to set it up)
- i want no replication; i.e. single-node Garage (i'll redo my setup properly once i'm on better hardware)
- i use Cloudflare Tunnel to make my services available on my domain
- why i am trying to use Garage instead of the simple minIO block: minIO does not run on my "ancient" hardware
- the "ancient" hardware: 1c/2t Intel Atom 1.66GHz, <1GB RAM, 250GB SSD, Acer Aspire One netbook from ~2011
Was this page helpful?