Skip to content

Research on static file/serving platforms #9

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

Closed
wtrocki opened this issue Oct 6, 2020 · 4 comments
Closed

Research on static file/serving platforms #9

wtrocki opened this issue Oct 6, 2020 · 4 comments

Comments

@wtrocki
Copy link
Member

wtrocki commented Oct 6, 2020

Hi

I have done some preliminary work to seed discussion on static middlewares in Node.js.

I think we can have 3 categories for those:

Generally s3 dominating as a store.

There is also concept how to actually reference and store s3 files with auth in database but this is very specific and it is easier to google it rather than reference it here.

@mhdawson This might actually require some discussion on call.

@wtrocki wtrocki changed the title Research on file platforms Research on static file/serving platforms Oct 6, 2020
@mhdawson
Copy link
Contributor

mhdawson commented Oct 6, 2020

@wtrocki we will plan to discuss in an upcoming meeting.

@wtrocki
Copy link
Member Author

wtrocki commented Oct 7, 2020

Include deployment of the app that is changed - cache invalidation issue.

@roastlechon
Copy link
Contributor

Using bundler to produce static assets with hash in filename.
AND/OR
Using version in path of static asset so new version of Node app (serving the assets) will not result in poisoned/old cache of assets.

@wtrocki
Copy link
Member Author

wtrocki commented Oct 7, 2020

Done in #13 - Hope that is my lucky number :D

@wtrocki wtrocki closed this as completed May 19, 2021
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

3 participants