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
I got an express back end app that also serves a bunch of static files. Those static files could be probably better served by nginx directly. By pulling those out of the temporary zipfile that gets deployed the size of the file would be reduced dramatically. Is that possible by manually changing some configuration files and copying the files to a specific place?
The text was updated successfully, but these errors were encountered:
Method 1 (more efficient):
Use customized caching mechanism. The very first request for a static asset will go to your express app. But anything after that, until cache expires, will be served from nginx.
Note that in CaptainDuckDuck instance everything is containerized and cross contamination is very minimal. The nginx container has no access to files in your app container, therefore you cannot reference your app specific files, from your nginx config which lives in nginx container. The only link between nginx and your app is a normal HTTP connection.
I got an express back end app that also serves a bunch of static files. Those static files could be probably better served by nginx directly. By pulling those out of the temporary zipfile that gets deployed the size of the file would be reduced dramatically. Is that possible by manually changing some configuration files and copying the files to a specific place?
The text was updated successfully, but these errors were encountered: