Possible Dockerized setup config #40
Closed
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
…out for the B3. Was strictly an output problem
|
I'm not that familiar with how docker is supposed to work, but I understand it's supposed to be pretty good. Is there anything to be careful of in future development to avoid breaking the docker install? |
|
It should be fairly robust to internal changes in the software that don't change the interface, save the commits I linked to above, which fiddle with the default paths. Changes to the install process (using a different HTK version, etc) would be more dangerous, but |
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 option to use Docker (www.docker.com) to install and run FAVE (focused on FAVE-align). Haven't tested thoroughly on FAVE-extract, but most FAVE-align workflows are functional. Introduces minor path modifications in 7e1c32e and 77a8cf1 that are possibly breaking for non-Dockerized cases, though I imagine they are fine.