Maintain pywps demo with cookiecutter?

[cehbrecht]

Description

We are using a cookiecutter to setup new pywps projects:
https://github.com/bird-house/cookiecutter-birdhouse

Should we use the cookiecutter to maintain this pywps demo?

Should Flask be an optional part of the cookiecutter?

Potentially we could also move the cookiecutter-birdhouse to the geopython repo as cookiecutter-pywps.

This demo could also replace the Emu WPS:
https://github.com/bird-house/emu

Environment

• operating system:
• Python version:
• PyWPS version:
• source/distribution
• git clone
• Debian
• PyPI
• zip/tar.gz
• other (please specify):
• web server
• Apache/mod_wsgi
• CGI
• other (please specify):

Steps to Reproduce

Additional Information

[cehbrecht]

@jachym @jorgejesus @huard Thoughts?

[huard]

Emu is playing the role of a sandbox for new ideas. Is this compatible with the demo concept where things should be as simple as possible and work smoothly for first time users ? If yes, then I'm all for it.

[cehbrecht]

Emu is playing the role of a sandbox for new ideas. Is this compatible with the demo concept where things should be as simple as possible and work smoothly for first time users ? If yes, then I'm all for it.

That is a point. So we may have a pywps demo (the current pywps-flask) and the Emu WPS for showing and exploring new pywps features. But it would be nice if we get the demo easier maintained ... using the cookiecutter. We can also check if we like to move some processes from Emu to demo.

[jachym]

Merging of both would be beautiful. pywps-flask with the demo.py is currently, as I understand it, obsolete, with the new daemon functionality in pywps-server. but we are using it for integration tests and as list of sample processes.

can we merge both projects somehow together?

[cehbrecht]

We can create this demo again using the cookiecutter template. But we need to manually add the flask extension with the page for the process list.