Issue 16

[jorgejesus]

Overview

Implements issue #16 (Implementaition of PYWPS_CFG and PYWPS_PROCESSES). The demo.py script will pick up the variables from system env and use it. Unitests was write and located in tests/test_variables.py

Related Issue / Discussion

@tomkralidis Is it necessary for the directory in PYWPS_PROCESSES to be checked for changes and automatically reloaded or is it enough to restart pywps4-flask with a new PYWPS_PROCESSES

There is also a #11 request that needs evaluation based on changed of #51

Additional Information

test_variables.py doesn't used a live server, and will just make some requests to wps() on demo.py and check that temporary PYWPS_PROCESSES and PYWPS_CFG were accepted

Travis was updated but requires a bit more attention

Contribution Agreement

(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

• I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
• [x ] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

[tomkralidis]

Thanks @jorgejesus. It's enough to restart pywps4-flask with a new PYWPS_PROCESSES.

[cehbrecht]

Code changes look fine ... but I haven't tested.

[cehbrecht]

@jorgejesus The feature to load processes from a directory is useful in general and we might want to have it in pywps itself (again) ... could be added as an option. It would be kind of a plugin mechanism. A simple implementation to start with is fine.

Also we could move the usage of PYWPS_CFG environment variable to pywps.

[jorgejesus]

@jorgejesus The feature to load processes from a directory is useful in general and we might want to have it in pywps itself (again) ... could be added as an option. It would be kind of a plugin mechanism. A simple implementation to start with is fine.

Also we could move the usage of PYWPS_CFG environment variable to pywps.

I can open a ticket on pywps for introducing a plugin structure for processes and reintegration of PYWPS_CFG

[cehbrecht]

@jachym @jorgejesus @tomkralidis Should we merge this PR? ... or take it as an example and implement it pywps geopython/pywps#118.

It has a new example process TotalLength ... but could be added in another PR.

[jachym]

this is an oldone - don't we have already code for automatic process import in the master branch ? processes configuration option, which is pointing to Python module?

[cehbrecht]

this is an oldone - don't we have already code for automatic process import in the master branch ? processes configuration option, which is pointing to Python module?

yes. We could extend it to load processes from a file path, like done in this PR.

[jorgejesus]

@cehbrecht, @jachym is this PR still valid/important or we can trash it ?

[cehbrecht]

I think we don't want to merge it but keep it as reference for the implementation of the processes_path (geopython/pywps#118).