Skip to content
Snippets Groups Projects
Select Git revision
  • claims-in-idtoke
  • master default protected
  • jwt_encode_inconsistencies
  • recovery-code-pwhash
  • incremental-sync
  • redis-rate-limits
  • typehints
  • v1.2.x
  • v1.x.x
  • v1.1.x
  • feature_invite_validuntil_minmax
  • Dockerfile
  • v1.0.x
  • roles-recursive-cte
  • v2.3.1
  • v2.3.0
  • v2.2.0
  • v2.1.0
  • v2.0.1
  • v2.0.0
  • v1.2.0
  • v1.1.2
  • v1.1.1
  • v1.0.2
  • v1.1.0
  • v1.0.1
  • v1.0.0
  • v0.3.0
  • v0.2.0
  • v0.1.5
  • v0.1.4
  • v0.1.2
32 results

debian

  • Clone with SSH
  • Clone with HTTPS
  • Forked from uffd / uffd
    87 commits behind the upstream repository.
    Julian Rother's avatar
    Julian authored
    CONFIG_FILENAME works relative to the app's instance path. While (strictly
    speaking) CONFIG_FILENAME is named correctly, it is not really obvious that
    it should be set to an instance-relative filename instead of a path. The
    current uwsgi.ini file illustrates this problem.
    
    Not having a way to specify an absolute config file path is a problem for
    the Debian package: The actual config file /etc/uffd/uffd.cfg must be
    symlinked to /usr/share/uffd/instance/config.cfg to be found. Setting
    CONFIG_PATH to "/etc/uffd/uffd.cfg" simplifies this.
    
    Since this change is part of a new major release, we can drop
    CONFIG_FILENAME in favour of CONFIG_PATH.
    73c9b77e
    History