You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A docker image is automatically built using GitHub actions whenever a version tag is pushed. See the GitHub-hosted [compmicro-ndutils-env](https://github.com/czbiohub-sf/compmicro-ndutils-env/pkgs/container/compmicro-ndutils-env) Docker repository.
19
+
20
+
To pull and run a Docker image:
21
+
```
22
+
docker run ghcr.io/czbiohub-sf/compmicro-ndutils-env:${VERSION}
You can check the version of the installed ndutils environment using the ndutils_version command or with "pip list"
44
+
You can check the version of the installed ndutils environment using the env_version command or with "pip list" or "pip show".
45
+
26
46
```
27
-
$ ndutils_version
28
-
0.2.0.dev2
47
+
$ env_version
48
+
ndutils 0.2.0.dev3
29
49
30
50
$ pip list | grep ndutils
31
-
compmicro-ndutils-env 0.2.0.dev2
51
+
ndutils 0.2.0.dev3
52
+
53
+
$ pip show ndutils
54
+
Name: ndutils
55
+
Version: 0.2.0.dev3
56
+
Summary: ndutils compute environment for computational microscopy at CZBiohub SF
57
+
...
32
58
```
59
+
60
+
## Creating a new release
61
+
To update this environment:
62
+
* Check out the git repo and make edits
63
+
* Update Python dependencies by editing requirements.txt (which is used by Conda, Docker, and Pip install methods)
64
+
* Update Python version by editing both environment.yml (for Conda) and Dockerfile
65
+
* Commit and push/merge changes to the *main* branch
66
+
* Tag the commit with a version identifier (`git tag x.y.z`)
67
+
* Push the tag with `git push --tags` (warning this pushes ALL local tags)
68
+
* Monitor [GitHub actions](https://github.com/czbiohub-sf/compmicro-ndutils-env/actions) to confirm the build succeeds
69
+
* If needed, deploy the new environment to your infrastructure (e.g. by running "conda update ...".) Deployment documentation is not included here as it varies between sites.
70
+
71
+
## Creating a new environment
72
+
If you want to use the code in this repo as a template for creating a new environment, you will need to make the following changes:
73
+
* Create a new repo in GitHub. (Defining multiple environments in one GitHub repo is to be avoided because it complicates versioning and automatically building each environment separately.)
74
+
* When copying files into the new repo, be sure to include the hidden ".github/" directory and ".gitignore" file, but exclude the ".git/" directory. (A fresh ".git" directory will be creating either by `git init` or by cloning a clean repo created in GitHub.)
75
+
* Edit the following files and directories to update references to the git repo name (compmicro-ndutils-env), Python package name and conda environment name (ndutils), environment name. (You may want to grep to make sure there are not any others.)
76
+
* README.md
77
+
* pyproject.toml
78
+
* ndutils/
79
+
* Edit the Dockerfile to ensure an appropriate ENTRYPOINT is used, if any, for the new environment.
80
+
* Commit, tag, and push the updated code as described in "Creating a new release".
0 commit comments