Added pueued.plist to support daemon with launchd on macOS #429
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
Binaries that're compressed via upx tend to trigger the windows defender and other anti-virus programs. To prevent these false-positives, the windows binaries won't be compressed any longer. Fixes #421
Bump deps
Added pueued.plist file which contains comments on how to launch the daemon on macOS with launchd.
|
I can't test this, but it looks good to me :) Thanks for your contribution! |
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.
Instructions for running the daemon with launchd are in the comments of the file.
The wiki could be extended with 'Get started -> Start the Daemon -> Launchd' with the informations from the comments.
This is my first pull request ever, so I hope I gave every information needed and adhered to the form of a pr. 馃槉
Thanks for sending a pull request!
Here's some info on how development works in this project:
The
mainbranch is the version of the last release.patchlevel PRs, for example bugs or critical library updates, should be merged intomaindirectly.A new
patchrelease is usually published shortly after the PR is accepted.New features should branch of the
developmentbranch. \Checklist
CHANGELOG.md.cargo clippyandcargo fmt. The CI will fail otherwise anyway.