#116 Dockerfile: running waiverdb with uwsgi
Closed 2 years ago by dcallagh. Opened 2 years ago by mjia.
mjia/waiverdb uwsgi  into  master

file modified
+4 -3
@@ -1,4 +1,4 @@ 

- FROM fedora:26

+ FROM fedora:27

  LABEL \

      name="WaiverDB application" \

      vendor="WaiverDB developers" \
@@ -10,11 +10,12 @@ 

  COPY $waiverdb_rpm /tmp

  COPY $waiverdb_common_rpm /tmp

  RUN dnf -y install \

-     python-gunicorn \

+     uwsgi \

+     uwsgi-plugin-python \

      python-psycopg2 \

      /tmp/$(basename $waiverdb_rpm) \

      /tmp/$(basename $waiverdb_common_rpm) \

      && dnf -y clean all

  USER 1001

  EXPOSE 8080

- ENTRYPOINT gunicorn --bind 0.0.0.0:8080 --access-logfile=- waiverdb.wsgi:app

+ ENTRYPOINT uwsgi --http-socket :8080 --master --processes 8 --plugin=python -w waiverdb.wsgi:app

no initial comment

Whaddya think, @dcallagh? Is this still desirable if we can proceed with krb5 in OpenShift?

I think it's good to see what changes would be needed here (and the alternative #117) so thanks to @mjia for putting these up. However I think for now we should abandon both these PRs under the assumption we can stick with Kerberos.

I've got both these PRs linked in our internal JIRA issue about the SSL cert auth, so we can find these and resurrect them later if needed.

I think it's good to see what changes would be needed here (and the alternative #117) so thanks to @mjia for putting these up. However I think for now we should abandon both these PRs under the assumption we can stick with Kerberos.

I've got both these PRs linked in our internal JIRA issue about the SSL cert auth, so we can find these and resurrect them later if needed.

Oh Pagure, why so buggy...

Pull-Request has been closed by dcallagh

2 years ago

Build 22e50a06d25a28e9978d8ef85fa089548a821bed FAILED!
Rebase or make new commits to rebuild.

Build 22e50a06d25a28e9978d8ef85fa089548a821bed FAILED!
Rebase or make new commits to rebuild.

Metadata