Heroku compatibility #1109
Closed
Heroku compatibility #1109
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
ahilles107
force-pushed
the
heroku_compatibility
branch
from
e51fa49
to
aaeda68
Compare
|
I would wait until the original PR gets merged instead of using the fork, it's not a blocker |
|
It blocks dependencies update for now. But we can wait. |
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.
Proposed Changes
Support Elasticsearch 6.x
THIS CHANGE REQUIRE ELASTIC SEARCH INDEX REBUILD AFTER DEPLOYMENT
Command to import themes to publisher (useful in environments without persistent strage)
Themes can be downloaded on build stage
Support heroku (commands in compile scripts)
Use forked guzzle (solves [6.5] Fix various intl icu issues guzzle/guzzle#2626).
License: AGPLv3