Skip to content
Snippets Groups Projects
Select Git revision
  • develop default protected
  • 1356-update-packages
  • 1303-failing-to-refetch-federated-tracks
  • 1108-remove-jwt-and-switch-to-oauth-for-ui-auth
  • set-sast-config-2
  • set-sast-config-1
  • master
  • tracemallocmiddleware
  • 1299-encoding-problem-in-rss-feeds
  • 1346-selectoreventloop-required-instead-got-uvloop-loop
  • 1278-embed-isn-t-available-in-the-front-end-for-channel-tracks
  • 1311-feedparser-requires-update-to-accomodate-python-3-9
  • 1.0.1
  • 1121-download
  • plugins-v3
  • plugins-v2
  • plugins
  • 1.1.1
  • 1.1
  • 1.1-rc2
  • 1.1-rc1
  • 1.0.1
  • 1.0
  • 1.0-rc1
  • 0.21.2
  • 0.21.1
  • 0.21
  • 0.21-rc2
  • 0.21-rc1
  • 0.20.1
  • 0.20.0
  • 0.20.0-rc1
  • 0.19.1
  • 0.19.0
  • 0.19.0-rc2
  • 0.19.0-rc1
  • 0.18.3
37 results

notes.rst

Blame
    • Forked from funkwhale / funkwhale
    5954 commits behind the upstream repository.
    notes.rst 963 B

    Next release notes

    Note

    Those release notes refer to the current development branch and are reset after each release.

    Avoid mixed content when deploying mono-container behind proxy [Manual action required]

    You are only concerned if you use the mono-container docker deployment behind a reverse proxy

    Because of an issue in our mono-container configuration, users deploying Funkwhale via docker using our funkwhale/all-in-one image could face some mixed content warnings (and possibly other troubles) when browsing the Web UI.

    This is fixed in this release, but on existing deployments, you'll need to add NESTED_PROXY=1 in your container environment (either in your .env file, or via your container management tool), then recreate your funkwhale container.