ltmanage in bin #580
Merged
ltmanage in bin #580
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows using the api key instructions from the readme as-is in the docker container.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows using the API key instructions from the read-me "as-is" in the docker container.
See also https://community.libretranslate.com/t/where-do-i-find-ltmanage-command/406
I also corrected the path to the keys db in the docker compose file comments, otherwise it did not work in my setup:
libretranslate_api_keys:/app/db/api_keys.db->libretranslate_api_keys:/app/dbTests: For some reason, on my localhost, the api-keys option did not block requests done through the UI (event before my changes). So, I tested by rate-limiting users to 0/minute and creating an API key that allows 120/minute.
A similar setup could be done for cuda version.