[2.5.1]
Update libretranslate to 1.7.3
Full Changelog
Fix --url-prefix by @SuperSandro2000 in https://github.com/LibreTranslate/LibreTranslate/pull/830
Fix permissions error when running CUDA Docker by @enoch85 in https://github.com/LibreTranslate/LibreTranslate/pull/834
PDF support by @pierotofy in https://github.com/LibreTranslate/LibreTranslate/pull/839
Update index.html by @BoFFire in https://github.com/LibreTranslate/LibreTranslate/pull/848
Update manage.py by @BoFFire in https://github.com/LibreTranslate/LibreTranslate/pull/850
Add support for Python 3.13 by @progval in https://github.com/LibreTranslate/LibreTranslate/pull/855
Ah thanks for the hint, the latest package uses virtual env now, so we had to update the docs to initialize the python venv with source /app/code/.venv/bin/activate.
The docs are now fixed https://docs.cloudron.io/apps/libretranslate/
Oh indeed, my entire answer is wrong (thanks @necrevistonnezr ).
You have to set LT_REQUIRE_API_KEY_ORIGIN=true in the configs - https://docs.cloudron.io/apps/libretranslate/#api .
@nebulon
I think Mastodon's translate button only appears if the poster has set a language for his / hear toot that's different from your language settings.
It could be that the LT API relies on the source and destination language settings that are submitted by Mastodon. That could be an explanation for the errors I received, b/c not everyone sets the language correct. Maybe the DeepL API is more flexible here.
@LoudLemur that is indeed strange, Cloudron only reports a running state if the healthcheck succeeds which for libretranslate means that the api and frontend server is up and running.
