Open
Conversation
Contributor
|
@hlubek We are running |
Member
Author
|
@Benjamin-K Hi, this is only about the script that is being managed by Composer and needed some special workarounds with The Prunner process itself can still run outside of this package as before. |
Contributor
|
This might relate to FEATURE: connect to existing Prunner system service. The Prunner binary is no longer installed via composer (opt-out). |
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
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.
Move custom wrapper script to a Composer script to have it in ´bin/prunner` (like expected for a Composer package) and errors on install.
Question: Calling
bin/prunneroutside of the project root doesn't work correctly with this approach. Does this matter for us?