The current Docker image uses the default NGINX configuration, which does not define any cache-control behavior. This can lead to stale or broken UI states after deployments due to aggressive browser caching of index.html or inconsistent caching of static assets.
It would be helpful to provide a default nginx.conf as part of the project that:
- Ensures index.html is never cached (or always revalidated)
- Enables long-term caching for hashed static assets (JS/CSS/fonts)
- Ensures unhashed static data (static/*) is not cached
- Optionally other stuff
The question is whether we should include such a default configuration or leave customizations to our specific Wegue apps?
And if yes, where should those configurations live? Should we put a default.conf on the top project level or in some separated /nginx folder?
The current Docker image uses the default NGINX configuration, which does not define any cache-control behavior. This can lead to stale or broken UI states after deployments due to aggressive browser caching of index.html or inconsistent caching of static assets.
It would be helpful to provide a default nginx.conf as part of the project that:
The question is whether we should include such a default configuration or leave customizations to our specific Wegue apps?
And if yes, where should those configurations live? Should we put a default.conf on the top project level or in some separated /nginx folder?