Jan
Jan
Image lambda could be also single one, would just need access to different buckets. Which can be handled on stack-level.
There is ongoing issue with newer Construct not supporting region specification. This leads to the need for having 2 different stacks (one for application in preferred region and second in...
Hey! `_next/data` are basically API route I believe. It's handled by Next's server. ``` '_next/data/*': { ...defaultOptions, origin: serverOrigin, }, ``` What seems weird is that doubled `//` in your...
@js-sapphire I tried replicating without much luck :/ could you try to share repo steps? I will try to support you, however, please consider EOL (#97) for this package.
Closing, inactive :)
To address complexity concern, I was able to create lambda-only implementation of NextJS deployment to AWS. See: https://github.com/sladg/lambda-server-adapter/blob/master/examples/Next.md. I will probably publish terraform module later on to deal with optional...
Heya! I put it on side without ETA. Ultimately, i would need example project implementing it extensively so I can try it out :)
@pinarruiz yeah! if you have some project on hand we could use for testing and debugging, that would be perfect!
@pinarruiz quick followup. The way to implement ISR nowadays is going with `incrementalCacheHandlerPath`. I'm trying to document these over here: https://github.com/sladg/doc-next-lambda.
Yeah, ApiGw expects Host to be Cloudfront. We would need to do mapping of original Host to something like X-Host. I would need to take a look what is recommended...