Support running from PHAR #55
Merged
Conversation
This file contains hidden or 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
SimonFrings
approved these changes
Jan 11, 2022
This was referenced Feb 13, 2022
Closed
This was referenced Apr 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 changeset adds support for running from PHARs. This works out of the box without any special configuration by running the SQLite worker like this internally:
The updated test suite confirms this works across all supported platforms, including Windows (which requires some special care). Windows tests on PHP < 7.3 may currently be skipped because building the PHAR fails due to clue/phar-composer#116, but execution should work just fine in either case.
Resolves / closes #5
Builds on top of #50, #45, clue/phar-composer#123 and others