Don't set ASSET_HOST environment if no asset host configured #302
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
This change avoids setting the ASSET_HOST environment variable in the compilation rake task if no asset host is set in Rails' configuration. Previously, if no asset host was configured, this environment variable would be set to an empty string, which caused the default `ifHasCDN` check in `configuration.js` to always return `true` in production.
|
thanks @mattmacleod 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change avoids setting the ASSET_HOST environment variable in the compilation rake task if no asset host is set in Rails' configuration.
Previously—introduced in #224—if no asset host was configured, this environment variable would be set to an empty string, which caused the default
ifHasCDNcheck inconfiguration.jsto always returntruein production.