uwsgi (2.0.28-3) unstable; urgency=medium

  Dropping plugin registration in the Debian alternatives system

  It was previously possible to configure the loaded plugin using symlinks
  to /usr/bin/uwsgi with those symlinks managed using the Debian alternatives
  system. While this is still possible, it is preferred to use configuration
  files.

  In order to simplify packaging, systematic registration of plugin binary
  as /usr/bin/uwsgi alternative has been dropped.

  See /usr/share/doc/uwsgi/README.Debian.gz for the procedure to reinstate this
  manually for your plugin of interest.

 -- Alexandre Rossi <niol@zincube.net>  Mon, 27 Jan 2025 16:54:10 +0100

uwsgi (2.0.26-4) unstable; urgency=medium

  Dropping apache2 modules, supplemented by mod_proxy_uwsgi.

  mod_uwsgi and mod_Ruwsgi are not longer provided. mod_proxy_uwsgi should
  be able to replace any usage of those modules. mod_proxy_uwsgi is available
  in the libapache2-mod-proxy-uwsgi binary package.

  apache2 configuration example for TCP:

      ProxyPass /foo uwsgi://127.0.0.1:3032/
      ProxyPass /bar uwsgi://127.0.0.1:3033/

  apache2 configuration example for Unix domain sockets:

      ProxyPass /foo unix:/var/lib/uwsgi/app1.sock|uwsgi://uwsgi-uds-app1/
      ProxyPass /bar unix:/var/lib/uwsgi/app2.sock|uwsgi://uwsgi-uds-app2/

  Full documentation is available at
  https://uwsgi-docs.readthedocs.io/en/latest/Apache.html#mod-proxy-uwsgi

 -- Alexandre Rossi <niol@zincube.net>  Wed, 21 Aug 2024 12:37:42 +0200

uwsgi (2.0.18-5) unstable; urgency=medium

  Deprecating the matheval plugin: plugin is deprecated upstream.

  In your configs, you can replace its use with simple math
  in configuration files. For instance, if you used to do:

      foo = 41
      plugins = matheval
      route-run = log:foo = ${math[%(foo)+1]}

  this becomes:

      foo = 41
      route-run = log:foo = %(%(foo) + 1)

 -- Alexandre Rossi <alexandre.rossi@gmail.com>  Sun, 06 Oct 2019 17:50:40 +0200

uwsgi (2.0.17.1-10) unstable; urgency=medium

  * Unix sockets are now readable by www-data by default,
    (option chown-socket),
    independent of runtime user/group.

    Users running backend services under separate user (option uid)
    can stop weaken isolation for frontend server (options gid/umask).

    Users with need for special access from frontend services
    now likely need to (also or instead) override option chown-socket.

 -- Jonas Smedegaard <dr@jones.dk>  Mon, 10 Dec 2018 20:26:13 +0100

uwsgi (2.0.17.1-3) unstable; urgency=medium

  * uwsgi can no longer be disabled in /etc/default/uwsgi.
    Disable it using the command 'update-rc.d uwsgi disable'.

 -- Jonas Smedegaard <dr@jones.dk>  Sat, 15 Sep 2018 02:20:21 +0200

uwsgi (0.9.8.3-2) unstable; urgency=low

  Locations of runtime directory of uWSGI instance and logfiles are changed.

  In previous package' versions runtime files of uWSGI instance were located at
  directory

    /run/uwsgi/<confname>

  Now, they are located at directory

    /run/uwsgi/app/<confname>

  So, communication UNIX socket of uWSGI instance is now located at
  '/run/uwsgi/app/<confname>/socket'. It is necessary to make appropriate
  changes in upstream server configuration (if any). Otherwise upstream server
  will be unable to communicate to uWSGI and behavior of whole web-application
  stack will be broken.

  Logfile location is changed from

    /var/log/uwsgi/<confname>.log

  to

    /var/log/uwsgi/app/<confname>.log

 -- Leonid Borisenko <leo.borisenko@gmail.com>  Wed, 27 Jul 2011 17:39:06 +0300