Remove appu command in favor of a docker run #89
Merged
Conversation
This file contains hidden or 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
ifosch
force-pushed
the
separate-cfg-creation
branch
from
a853629 to
3e2dcc3
Compare
Now epidator creates the episode YAML file, instead of printing it out to stdout, so there's no need to redirect the output.
ifosch
force-pushed
the
separate-cfg-creation
branch
from
3e2dcc3 to
2181884
Compare
Member
Author
|
Closes #46 |
This was referenced Mar 8, 2025
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.
The appu command was responsible for creating the config file required
by the appu container, as well as downloading and preparing the files
to be mounted. Then, the appu command was running the appu container.
The files preparation are now responsibility of the epidator file,
which now also creates the episode YAML file. Then the appu container
can be run with the docker run command as documented in the README
file.