Conversation
There was a problem hiding this comment.
PR Overview
This PR updates the changelog to document the recent qiime updates and the installation of qiime2R.
- Updated changelog with version 0.1.2 to record the qiime upgrade and addition of qiime2R.
Reviewed Changes
| File | Description |
|---|---|
| terra-rstudio-aou/CHANGELOG.md | Added version 0.1.2 changelog entries for qiime enhancements |
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
terra-rstudio-aou/CHANGELOG.md
Outdated
| @@ -1,5 +1,9 @@ | |||
| # Changelog | |||
|
|
|||
| ## 0.1.2 - 2025-03-07 | |||
There was a problem hiding this comment.
Should this changelog and version control be for terra-jupyter-aou instead? I am alsways a bit confused about version control since there is a single image for both jupyter and r.
Would you be able to update the conf.json file accordingly?
There was a problem hiding this comment.
oh yea...updated the wrong file..good catch!
LizBaldo
left a comment
There was a problem hiding this comment.
You can use the GHA to build and publish the aou image you want to test to GCR, and then open a PR in Leo to test on a BEE.
That way you can merge this PR once your testing is done, let me know if you have any questions
|
ah cool...forgot it's a GHA for building the image now...will try that |
https://precisionmedicineinitiative.atlassian.net/browse/RW-12661
I was able to build the image locally, and running the image. But in order to verify if qiime is installed properly, I'll need to install a jupyter-server extension and upgrade jupyter-server, which I wasn't able to do locally. The main reason is because after installing the server extension, it requires restarting the jupyter server. But if we restart the jupyter server, the docer container will restart and losing the extesion. Lmk if you have suggestions how to test this. If not, I'd like to get this merged in, have the image generated and uploaded to GCP so that I can test things a bit better in a BEE