You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it is assumed that lambda will be used as the source of compute for the NextjsDistribution construct. Instead of passing serverFunction and imageOptFunction directly into this construct, what if it was abstracted away and serverHttpOrigin and imageOptOrigin were passed into the construct such that other types of compute could be defined by user and passed in?
I likely won't have time to implement this, but said I would create this issue in #108. Wanted to create the issue in case someone else wanted to implement.
The text was updated successfully, but these errors were encountered:
bestickley
changed the title
Allow Different Types of Compute Than Lambda
Allow Different Types of Compute Other Than Lambda
May 30, 2023
Currently, it is assumed that lambda will be used as the source of compute for the
NextjsDistribution
construct. Instead of passingserverFunction
andimageOptFunction
directly into this construct, what if it was abstracted away andserverHttpOrigin
andimageOptOrigin
were passed into the construct such that other types of compute could be defined by user and passed in?I likely won't have time to implement this, but said I would create this issue in #108. Wanted to create the issue in case someone else wanted to implement.
The text was updated successfully, but these errors were encountered: