-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMPROV] Quality of Life improvments for the devcontainer #163
Conversation
Still need to update all documentation 😜 |
Documentation should be updated ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, that's really nice! 💯 I just tested it, and it truly makes it much easier to develop within the container (even on Mac...). I encountered only one bug, which I described below. Otherwise, it looks pretty good to me!
|
||
ignore [".venv/*"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems the ignore flag is not available in the current release of nf-test
(0.8.4). When I try to run a test for a module, it outputs this error message:
Error: Syntax errors in nf-test config file: groovy.lang.MissingPropertyException: No such property: ignore for class: com.askimed.nf.test.config.Config
I quickly went through the nf-test repo, and it seems the ignore was commited last month for the 0.9.0 release. I also might be wrong 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GTG
Type of improvement
If submitting a new module or fixing a bug, please use the appropriate template.
Describe your improvement
Quality of life improvements for the development container :
NFCORE_*_GIT_REMOTE
andNFCORE_*_BRANCH
. No need to add--git-remote
or--branch
to thenf-core
commands inside the container anymore.venv
python environment inside the workspace. We'll ignore it everywhere we can, but it must live there forvscode
to detect it correctly.user profile
persistence (command history should carry between rebuilds). Requires to rebuild the container once, so the volumes get instantiated and linked to the container by docker.nf-test
folder living inside the workspace in its own volume, so we can delete it easily if the container runs out of space and does want to startNiiVue
to the extensions stack. Enjoy looking at images from insidevscode
now ! Now, when you click on a nifti in the explorer, it opens in a 3D (even 4D !) viewer in the editor. The 3D mean intensity projection view is quite nice, ! But it does handle all space transformations perfectly yet, doesn't have peaks, nor fodf, nor tensors and is limited in sense of colormaps. Still, very nice to have in the container..devcontainer
folder does)Describe how to test your improvement
Remove all containers and volumes related to the
nf-scil
devcontainer from docker. All resources should be prefixed withnf-scil
. You won't loose your work, but you'll loose any cache living outside the workspace folder.Checklist before requesting a review