Support for Bitbucket would make a great addition. The payload for Webhooks has changed recently and its definition can be found here.

Release v0.9.0 is mentioned in commits, changelog and README.md, but it's not tagged. Therefore the link to the release doesn't work and users download an old version.

Could you please tag version v0.9.0?

I finally managed to get this to work with Gitlab.
I think having a little more documentation (and also fixing some of the outdated remarks) would really help.

Example for outdated (or even wrong?!):

You can test this by calling /admin/ (protected by .htaccess, only works localy)

The way I managed to get it working the admin page is available at https://deploy.example.com/app/admin/public and is not available only for localhost. The .htaccess includes Allow From All.

Also the release download link is not working.

I noticed that there is a fork (https://github.com/natronite/deepl.io) which has some good improvements (e.g. allowing IP Ranges instead of single IPs only) - any plans to incorporate those commits?

I've changed the config.json to have a special token and added all the files from the repo to deploy.domain.org. The index page says the mod_rewrite and .htaccess are working and config.json: Found and well formated.

I added the webhook url as http://deploy.domain.org/token but I keep getting a 301 with nothing the body and metadata:

Connection: close Content-length: 0 Location: https://deploy.domain.org/token/

Is the problem that it is trying to access https which isn't working? There are no logs in the logs folder either.

I am also not sure if my repositoriesPath variable is correct. Could that be the reason for the payload failure?

Thanks!

Is there support for nginx or a config file to reference or do I need to convert htaccess files on my own?

I'm new to Git, but I'm learning as I go. So thanks for trying your script :) Though I have some difficulties getting it work (I have no idea if the problems occur because of mod_rewrite or php exec).

My story:

1. Script is cloned via Github and is located at www.mydomain.com/deploy
2. Webhook made on GitHub and is set as www.mydomain.com/deploy/ (the token set in config)
3. The same key is set as secret in the hook. application/json is set, trigger is just "push the event" and Active is checked.

When doing this and pushing to master I unforunately get 404 error under webhooks in Github:

Request URL: http://www.mydomain.com/deploy/
Request method: POST
content-type: application/json
Expect:
User-Agent: GitHub-Hookshot/8b1477d
X-GitHub-Delivery: 20386c80-20e0-11e5-8205-db9ea32af80c
X-GitHub-Event: push
X-Hub-Signature: sha1=063617fb859c437a40a4076ef616985ac662c77f

Content-Length: 0
Content-Type: text/html
Date: Thu, 02 Jul 2015 17:33:03 GMT
Server: Apache/2.2.16
Vary: Accept-Encoding

deepl.oi error log says this:

[2015-07-02 19:33:04 - IP 192.30.252.34]
[ERROR] Security token not correct: deploy/
[STATUS] FAILED – Deployment not finished!
[NOTR] No mails configured.

Can you figure out what is wrong with this? I think it's strange. It looks like the token is incorrect, but it certainly is not. However, it's strange it thinks that the deploy folder (path to deeplio) is a part of the token?

Any ideas, please? :)

Cheers!

Hi there,

Have just been playing around trying to get deepl.io working, and after stepping through the source to fix configuration issues (on my end), I think I've finally come across an actual bug.

It looks like the BitBucket payload doesn't include a "ref" param at all, which means that the check against /refs/heads/{branch-name} in 9a83751 is now failing.

Not sure if that commit could just be reverted, or if it'll need to be updated to be more cross-service compatible.

I pull up the deepl.io install on my server just fine:
https://dashdev.waynation.com/twister

but when I add my secret token to the end I get a 404 error