Hi,

I use gunicorn in my venv

I have quite few venv that run gunicorn.

I would like to reuse gunicorn for other venv

I launch my web application like this

#PWD = venv dir
source ./bin/activate
gunicorn A_WebApp:app
#A_WebApp is my python file A_WebApp.py

I supposes that gunicorn is a shell program ? if yes I should use $PATH ?
or gunicorn is a Python program only ? and then what I should do to use gunicorn in another venv ?

Thanks.

  • _____@lemm.eeEnglish
    4·
    2 months ago

    If A_WebApp is truly the python file and app is some python symbol then you should be able to make gunicorn in another venv and call your script as such: path/to/venv/bin/python gunicorn A_Web_App:app

    • SpongeB0B@programming.devOPEnglish
      2·
      2 months ago

      Thank you ! it works !

      Actually this is working :

      path/to/venv/bin/gunicorn A_Web_App:app

      Some other poster, claim it’s dirty… but which problems could it generate ? (if any)

      Thanks all !!!

      • _____@lemm.eeEnglish
        1·
        2 months ago

        I don’t think it’s dirty if you manage your requirements across these environments with care, but I’d ask for what they mean

  • fraksken@infosec.pub
    1·
    2 months ago

    It’s possible to make the venv portable, versionize it, archive it and deploy at boot the latest version. It’s architecture dependent though, so if you deploy on multiple archs, you will need to build for each.

    Edit: gunicorn is part of the venv. All you need to do after deploying gunicorn is activating the venv and running your server.

    You can also have the archive tun through several vulnerability checkers.