Thibault RICHARD

Thanks for opening this PR. This is a pain and there is no correct way to handle this. For correct CORS handling, we would probably need to also add `access-control-request-headers`...

The server-side website is targeted at frameworks like Ruby on Rails, Symfony/Laravel, Django, Express, etc where the HTML rendering would be done server-side (with erb, twig/blade, DTL/Jinja, ejs/nunjucks, etc). What...

This is somewhat out of scope of this construct (at least for now). **Maybe** you could trick the construct by doing something like ```yaml constructs: website: type: server-side-website assets: '/css/*':...

First let me clear things up : I'm not trying to derail, what you're trying to accomplish seems like a thoughtful way to do (on several aspects like performance, costs,...

But that will only work for the homepage `/`, not other static routes right ? Or are other static routes fine with what we have now ?

Hi! Thanks for opening this issue. In Lift, we like to start discussions from the use case (the why) instead of the solution (the how) ? Could you describe the...

> The reason for needing the DLQ URL is to manually push messages to the DLQ when an error occurs which we know will not resolve on a retry. I'm...

> I think having two methods is a really good idea, that $fetch argument is confusing since a long time I think this is a great idea. It feels like...

@Nyholm I find this confusing, in https://github.com/brefphp/bref/pull/1032 you say > I also didnt want to remove docs how to use Bref with non-runtime symfony applications. That is why I added...

You are right, we should use the "registerables" thing to make sure we are on par with what was done previously and follow the documented way, though I couldn't find...