[Pywps-dev] demo.pywps.org continuous deployment setup

Tom Kralidis tomkralidis at gmail.com
Tue Sep 13 15:43:22 PDT 2016


Update: I've updated the deployment script to update either
demo.pywps.org or PyWPS proper depending on where the commit came
from.

Thanks Luís for the excellent suggestion.

..Tom

On Tue, Sep 13, 2016 at 12:10 PM, Tom Kralidis <tomkralidis at gmail.com> wrote:
> Hi all: our demo server at http://demo.pywps.org/ is now setup to be
> auto-updated on commits to master branch.
>
> The PyWPS demo repository [1] now has a GitHub Webhook script
> which listens to commits against PyWPS master branch.
>
> Basically, when a GitHub commit occurs, the script is triggered and:
> - updates master
> - does python setup.py install
> - touches the PyWPS/wps.wsgi file which auto-reloads the application
> without having to reload Apache
>
> The demo.pywps.org deployment runs on the OSGeo Adhoc
> infrastructure (see "Demo Server" in [3]).  There is a UNIX group
> pywps that jachym, tomkralidis, and www-data (to be able
> to auto-update the deployment) are part of (files/dirs are group
> writeable).
>
> The only diff being in
> /osgeo/demo.pywps.org/etc/apache/demo.pycsw.org which has the GitHub
> key (to which we shouldn't commit this change of course :).
>
> Please let us know if things don't work as expected.
>
> Cheers
>
> ..Tom
>
> [1] https://github.com/geopython/demo.pywps.org/
> [2] https://github.com/geopython/demo.pywps.org/blob/master/PyWPS/webhook-deploy.wsgi
> [3] https://github.com/geopython/pywps/wiki/TechnicalInfrastructure
>
> Cheers
>
> ..Tom


More information about the pywps-dev mailing list