[feat]: dockerized piper #93
Open
+321
−8
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
…semaphore based locking to limit local concurrency
allen-n
force-pushed
the
allen-n/dockerized-piper
branch
from
631d96a
to
c63cbd4
Compare
…xample docker compose file Remove unused import
allen-n
force-pushed
the
allen-n/dockerized-piper
branch
from
c63cbd4
to
a1745ad
Compare
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.
Adds a docker-compose config that simplifies using piper locally - though it does require the piper voice to be set in the docker compose yml, rather than as a command line argument.
Two usage modes exist: Passing the full set of command line args in the compose file (including the new
piper_dockertts engine), or running the container in interactive mode and calling main.py from there. Both are detailed in thedocker-compose.piper-example.yml.The clear benefit here is easy-mode usage of piper, regardless of machine. All that's required is cloning the repo, configuring the docker compose depending on which of the two options above is better suited for your use case, and running
docker compose up. Can confirm this works on an M1 Macbook Pro with no compatibility issues etc.