-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble deploying #9
Comments
Hey there, Are you still having problems with the payload? I forked this project a couple hours ago and made some changes to it, everything works perfectly fine for me now. I also added support for GitHub's secret to validate the payload. |
I'm struggling, but using Bitbucket rather than Github...what did you change? |
What issues are you having with Bitbucket? |
Outlined here: |
@DennisDreissen ended up using a script an engineer developed internally, but thanks for checking in on this. Will definitely try it again in the future. |
Hi!
I've been having some trouble getting the script to deploy even a public GitHub repo. I've been committing to this test repository without any luck: https://github.com/zalerner/deploy-test
The webhook appears to be delivering its payload based on the green check mark. Upon closer inspection it's getting a 200 response with this in the body:
I was wondering if this was potentially a configuration or permissions issue on my end. Here's my config:
The path is definitely right, but I wasn't sure about how much of the repo name was required. Unfortuantely, the deployments.log file isn't getting written to, and these initial PHP errors don't seem to be appearing anymore:
This is on a shared hosting environment where git is installed and I'm able to push/pull without any difficulty. Everything is owned by the primary FTP/SSH user. Any insight into what's happening would be huge!
Thanks for your time!
Zack
The text was updated successfully, but these errors were encountered: