Take a look at my repo if you’re looking for inspiration. I've fixed the build-time cache issue and reduced the final image to ~50MB. (I could shrink it further to around 20MB with static linking and by removing GCP functionality, but decided against publishing my atrocious "open-heart surgery". 50MB is... acceptable).
Discussion
yes, I am currently try to shrink the size, too. But I have problems with downloading the modules on the go proxy... somehow. Where to find your repo? Is it a fork?
I can need help, from a more experienced Docker dev. 🫂
Here you go: https://github.com/aaccioly-open-source/haven/tree/patch/reintroduce-docker. If you need anything deel free to DM me.
WOW! Ok, thank you very much. I was close, I was missing the setup of the cache directories. With GOCACHE and GOMODCACHE.
That's very nice with the extensions in your repo. I'm curious to see how big my images will be. But I have such bad download rates right now on Go-Proxy....
💪🤙😍
The cache and .docketignore files certainly help. `podman compose up --build` is only taking a few seconds for me after the initial build.
I think my VPN IP was blocked yesterday or throttled :-D Today it was faster with mod download.
The image now has only 17 MB 🫂🫂🫂
But I tried the blossom server with it: https://blossom.hzrd149.com/
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr This service does not support Blossom Servers with a "/path" like "/blossom" right. It cuts the path.
Haven Blossom server is reachable over the path "/blossom".
Blossom servers should only be reachable at the root path /
If its not on the root path its not really a blossom server
There are a few reasons for this, but mainly because things become 10x more complicated if you have to start specifying paths for services
Thanks for the help, nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr. I left a comment for you in khatru's CORS PR if you don’t mind taking a look.
Great stuff! For now, Haven is actually serving Blossom endpoints from the root (outbox relay). BLOSSOM_PATH is only being used as the internal path for saving files.
I’ve only tested Blossom support with noStrudel and it's working okay. I’ve tagged you in my current Nginx configurations (which will be removed soon) to add CORS headers and will ping you with any further updates.
Yes, thanks, I was misguided by that PATH and thought I had to use /blossom. In fact, I also have the CORS errors. Let's see the changes.