This repository has been archived by the owner on Jan 26, 2025. It is now read-only.
Update command flow add glide clear #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Updated package name and command registration for better consistency.
…tion and performance. Added cache clearing and regeneration steps, as well as clearing of media library and Glide cache.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces an update to the command flow in our deployment script by adding a call to
php artisan glide:clear. The motivation behind this change is to ensure that any cached Glide images are properly cleared during the deployment process, which helps prevent potential issues with stale images being served.Additionally, this update removes unnecessary cache clearing commands, streamlining the deployment process while still maintaining optimal performance. By focusing on clearing Glide images and optimizing the cache, we improve the reliability of our deployment and ensure that the latest assets are always served to users.
Overall, this change enhances the deployment workflow, reduces potential errors related to outdated cached images, and contributes to a smoother and more efficient release process.