Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain that the public folder is not local to the app folder at runtime #154

Open
macdonst opened this issue Jun 5, 2023 · 1 comment

Comments

@macdonst
Copy link
Contributor

macdonst commented Jun 5, 2023

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.

@tbeseda
Copy link
Contributor

tbeseda commented Jun 5, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants