Versioning not working at all
See original GitHub issueWhen I run .version()
under dev … the app.js file isn’t created, so that’s broke.
When I run it under production, Laravel doesn’t read the manifest for some reason and tries to deliver app.css
and app.js
which aren’t found.
Perhaps I need to change my Envoyer set up?
Right now I use npm run dev
in my local environment, and I have Envoyer hooks on my production server to install node modules and run Mix in production.
Do I need to change the flow of my deployments or is this going to get fixed so that it works as it did in version 5?
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (2 by maintainers)
Top Results From Across the Web
Enable and configure versioning for a list or library
Learn how to enable versioning on lists and libraries to track and manage information as it evolves. View and recover earlier versions and...
Read more >URL Versioning not working as expected in new ASP ... - GitHub
URL versioning is giving me back the following error stating that multiple endpoints match the request. This is happening when trying to use...
Read more >Swagger versioning is not working. It displays all endpoints ...
I need to create an endpoint for the new version of API and with the same route as a previous version. My controller...
Read more >File versioning is not working - Support - Syncthing Forum
It's not versioning files PC to Android, it does not keep any version of the file whatsoever. Staggered versioning is enabled on both...
Read more >Using versioning in S3 buckets - AWS Documentation
Normal Amazon S3 rates apply for every version of an object stored and ... When you enable versioning, existing objects in your bucket...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For anyone still coming to this thread: As of version 1.0
So don’t expect to have versioned files created. You’ll just have your app.js, main.css, etc. Query strings will be referenced in the manifest file that will handle the cache busting.
Concerning squid, from version 2.7, they no longer have the obsolete rule of not caching when query strings are used. I don’t know of any services on which query strings don’t work for cache busting. There are some services which require you to explicitly set that option though.