The cache and .docketignore files certainly help. `podman compose up --build` is only taking a few seconds for me after the initial build.

Reply to this note

Please Login to reply.

Discussion

I think my VPN IP was blocked yesterday or throttled :-D Today it was faster with mod download.

https://hub.docker.com/layers/holgerhatgarkeinenode/haven-docker/v1.0.0/images/sha256-0364ed61722038bf0a845ee886346dcb17dcb568546c76a8fa752bb5deb3fdec?context=explore

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.