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’ve encountered several issues when deploying code that worked fine in development mode. The problem stems from using JavaScript calls that aren’t versioned. In development mode, assets aren’t versioned, so the error only appeared when I deployed to production.
Even though the issue is due to a wrong call, I think a script like this: while true; do docker exec -it name_of_docker bin/console asset-map:compile inotifywait -e modify,create,delete -r assets sleep 1 done
could be very useful in avoiding such issues.
Do you see the usefulness and benefit of using tools like yarn watch to avoid unversioned assets in production deployments?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I’ve encountered several issues when deploying code that worked fine in development mode. The problem stems from using JavaScript calls that aren’t versioned. In development mode, assets aren’t versioned, so the error only appeared when I deployed to production.
Even though the issue is due to a wrong call, I think a script like this:
while true; do docker exec -it name_of_docker bin/console asset-map:compile inotifywait -e modify,create,delete -r assets sleep 1 donecould be very useful in avoiding such issues.
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions