Roeland Jago Douma
Merge pull request #277 from nextcloud/fixes
|1 week ago|
|config||1 week ago|
|docs||7 months ago|
|src||1 year ago|
|tests||1 week ago|
|vendor||3 years ago|
|.gitignore||7 months ago|
|.htaccess||3 years ago|
|.travis.yml||4 months ago|
|LICENSE||3 years ago|
|README.md||7 months ago|
|composer.json||7 months ago|
|index.php||7 months ago|
This is the server that is called from Nextcloud to check if a new version of the server is available.
If the tests are not passing the TravisCI test execution will fail.
Deployed URL: https://updates.nextcloud.org/updater_server/ Example call: updater_server/?version=9x0x0x12x1448709225.0768x1448709281xstablexx2015-10-19T18:44:30+00:00%208ee2009de36e01a9866404f07722892f84c16e3e
<?xml version="1.0" encoding="UTF-8"?> <nextcloud> <version>9.0.51</version> <versionstring>Nextcloud 9.0.51</versionstring> <url>https://download.nextcloud.com/server/releases/nextcloud-9.0.51.zip</url> <web>https://docs.nextcloud.org/server/9/admin_manual/maintenance/upgrade.html</web> </nextcloud>
If you wish to receive webhooks and then automatically deploy the lastest version of the updater server there is one special API endpoint available.
For this the Github Webhook needs to be configured to send
push events to the endpoint
/hook of the updater server. There only the ending part is crucial. That means that any URL ending in
/hook which is served by the
index.php of the updater server will trigger this behaviour.
Configure a webhook on Github in the repository of choice with
application/json as content type, a random secret and the
push event to be sent.
Then place a file
config/secrets.dist.php as example) with the same secret and the branch it should trigger on.
Once this is done the updater server will run a
git pull in the directory of the
index.php every time a valid event comes which matches the secret and then branch name. Keep in mind that the directory needs to be writable by the user under which PHP runs (most likely the webserver user).