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
Some folks have made the mistake of trying to read the /public folder like it was a local filesystem. The /app folder is deployed to a Lambda, while the /public folder is a S3 bucket. We should let folks know the best way to resolve this at runtime.
The text was updated successfully, but these errors were encountered:
Just 2 cents from my experience generally moving to a "serverless" architecture:
I had been running Node Express-style servers with middleware that served static assets out of a public folder.
When I started making cloud functions to handle integration tasks, it's not much of a shift since my main site was still either coming out of the Express app or it was static.
But having the whole app out of a series of Lambdas (Arc was my pick for this), there was a disconnect where I had to realize "oh yeah, this stuff is split up across resources that don't live on the same filesystem."
So, it's not just an Enhance thing, but a larger FWA paradigm shift.
Anyway, just anecdotal.
I think it can be helped with docs and maybe a diagram.
Some folks have made the mistake of trying to read the /public folder like it was a local filesystem. The /app folder is deployed to a Lambda, while the /public folder is a S3 bucket. We should let folks know the best way to resolve this at runtime.
The text was updated successfully, but these errors were encountered: