Closed keiranmraine closed 4 years ago
Image generated using the above approach
I wasn't completely clear on how this repository was structured with all the subfolders (you don't really need them under git).
The docker file builds the content of the v1.2.3 directory, so it would probably need modification if I've misinterpreted the structure.
Yes, I see your point -- When Rene makes a new release, he copies the scripts/files in their current state to a new directory named for the release.
I guess I'm wondering if the best thing would be to have the Dockerfile and the updated runCompareTwoGenomesColinear.sh
script in the main repo directory, and then we can update the newest version in the Dockerfile each time a new release is made? Would that make the most sense to you? The improvements to the runCompareTwoGenomesColinear.sh
script seem to be good, general changes that probably should be propagated to new releases.
I think this is the only line in the Dockerfile that we would have to update with a new released version?
ARG VER_FOLDER="v1.2.3"
yeah, that's poor organization. It was recommended we organize the repo in this fashion when we published the paper.. it is regrettable and now we're stuck with this.
Hi @keiranmraine,
So we have now deleted the version-specific directories to get rid of the unnecessary extra files. I think that will just mean that you'll have to tweak your Dockerfile, and push the changes to runCompareTwoGenomesColinear.sh
to the script in the base repository directory instead?
Replaced by #10 due to significant changes to master.
I've created a docker file which automatically add the fonts and exposes them via an env variable.
Running this shows that the test case doesn't exit with a 0 exit code (standard for success) when using
runCompareTwoGenomesColinear.sh
.I've made some minor modifications to
runCompareTwoGenomesColinear.sh
to test for programs and use the preinstalled fonts.