artisan lmsqueezy:listen #54
Merged
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
|
I worked on this a bit over the weekend but need to do some more testing/tweaking before I can merge this. Thanks! And sorry for the delay. |
Ha! No problem - I wasn't even expecting it to get merged, it was really just an exploration of an idea, but I watched the wip over the weekend with interest though. Thanks for considering it 👍 |
|
Thanks a bunch for this one. This will make getting started with webhooks so much easier. |
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.
If you plan to use Ngrok or Expose for handling incoming webhooks, consider utilizing the
artisan lmsqueezy:listencommand. This command not only streamlines the setup of a webhook through the Lemon Squeezy API but also ensures automatic removal of the webhook when you exit the command.Moreover, in case you encounter issues with webhook cleanup, you can always resort to the
--cleanupoption to remove any lingering webhooks associated with the same domains configured in Ngrok or Expose.