Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    David Huard
    @huard
    Let me know if you need a release, otherwise, the next one will probably be end of March.
    Cairo Sanders
    @cairosanders
    @cehbrecht yes, we posted that issue. I just wanted to see if anyone else ran into the same problem. Here is a branch I'm working off for the issue currently.
    Nils Hempelmann
    @nilshempelmann
    @/all
    Date and time for next VC is fixed:
    Apr 15. THU 14:00- 15:00 UTC
    https://github.com/bird-house/bird-house.github.io/wiki/Meetings
    MacPingu
    @cehbrecht
    The room is open: https://app.gotomeeting.com/?meetingId=751237301
    David Huard
    @huard
    @cehbrecht Should the cookie-cutter use gunicorn or some other wsgi server ? If I'm correct, at the moment it is using wekzeug.run_simple which is not recommended for production.
    MacPingu
    @cehbrecht
    @huard Currently we use the werkzeug for development and demo. In production we have gunicorn (ansible deployment). For the docker deployment this is probably not yet the case. No matter how we decide (could also be an option in cookie-cutter), I would like to keep the “start” with a “bird” simple … that is why I like the werkzeug.
    David Huard
    @huard
    Ok, slowly starting to understand how deployment works... not my forte. Agree we want to keep a simple demo version, but I think we should also include a default "prod" setup and expose it through docker. This could over time benefit from shared experience and optimisations.
    David Huard
    @huard
    wps_server_software_architecture (3).png
    @cehbrecht Does this diagram reflects correctly how birds are deployed via the cookie-cutter ?
    MacPingu
    @cehbrecht
    the cookie-cutter deployment relies on pywps/werkzeug only. There is also a dockerfile/docker-compose in the template. But we have not extended it for a production deployment with nginx, gunicorn, postgres.
    @huard your diagram reflects the ansible/docker deployment. There is also a more complicated image
    https://github.com/cehbrecht/birdhouse-talk-at-egu-2020/blob/master/media/cp4cds-wps.jpg
    David Huard
    @huard
    Thanks. I think we'll update the cookie-cutter with the nginx-gunicorn-postgres setup.py to provide a production-ready template.
    Nils Hempelmann
    @nilshempelmann
    @all If you have some minutes left, here is a text now online: https://www.ogc.org/blog/4460
    MacPingu
    @cehbrecht

    @all If you have some minutes left, here is a text now online: https://www.ogc.org/blog/4460

    :thumbsup:

    David Huard
    @huard
    @cehbrecht I think we're due for a birdy release. I've prepared a small PR. bird-house/birdy#204
    MacPingu
    @cehbrecht
    @huard approved … thanks for making the release :)
    David Huard
    @huard
    Done. Does it update on PyPi automatically ?
    MacPingu
    @cehbrecht

    Done. Does it update on PyPi automatically ?

    no. we have to upload it.

    Nils Hempelmann
    @nilshempelmann
    @cehbrecht Is Roocs able to handle unstructured grids?
    MacPingu
    @cehbrecht
    @nilshempelmann I think for subset/aggregate operator this is not an issue. We currently work on regridding … which has many issues … I can not say if some of the unstrutured grids work … unless I would currently say “no”.
    Nils Hempelmann
    @nilshempelmann
    :-) Thanks
    David Huard
    @huard
    @cehbrecht Is it possible the conda build for birdy is misconfigured with an extra "v" for the version ?
    This works: conda install -c conda-forge birdy==v0.8.1
    but conda install -c conda-forge birdy==0.8.1doesn't.
    David Huard
    @huard
    image.png
    MacPingu
    @cehbrecht
    @huard fixed. conda install -c conda-forge birdy==0.8.1 should work now.
    David Huard
    @huard
    Thanks !