-
Notifications
You must be signed in to change notification settings - Fork 124
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
Comments
@wtrocki we will plan to discuss in an upcoming meeting. |
Include deployment of the app that is changed - cache invalidation issue. |
Using bundler to produce static assets with hash in filename. |
Done in #13 - Hope that is my lucky number :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
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:
InApp
This is represented usually by underlying HTTP API. To name few examples:
https://expressjs.com/en/starter/static-files.html
https://www.tutorialsteacher.com/nodejs/serving-static-files-in-nodejs
https://nodejs.org/en/knowledge/HTTP/servers/how-to-serve-static-files/
Cloud (requires connectors like AWS S3 etc.)
This is what red hat is actually using in java frameworks a lot:
https://quarkus.io/guides/amazon-s3
Kubernetes (hybrid cloud solutions) that are s3 compatible - https://www.gluster.org/
This is red hat one: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html/operations_guide/s3_object_store
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.
The text was updated successfully, but these errors were encountered: