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
Copy file name to clipboardExpand all lines: README.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ One of the main goals is to make access to entire tool suites as easy as possibl
14
14
this includes the setup of a public available web-service that needs to be maintained, or that the Tool-user needs to either setup a Galaxy Server by its own or to have Admin access to a local Galaxy server.
15
15
With docker, tool developers can create their own Image with all dependencies and the user only needs to run it within docker.
16
16
17
-
The Image is based on [Ubuntu 22.04 LTS](http://releases.ubuntu.com/22.04/) and all recommended Galaxy requirements are installed. The following chart should illustrate the [Docker](http://www.docker.io) image hierarchy we have build to make is as easy as possible to build on different layers of our stack and create many exciting Galaxy flavors.
17
+
The Image is based on [Ubuntu 24.04 LTS](http://releases.ubuntu.com/24.04/) and all recommended Galaxy requirements are installed. The following chart should illustrate the [Docker](http://www.docker.io) image hierarchy we have build to make is as easy as possible to build on different layers of our stack and create many exciting Galaxy flavors.
@@ -115,6 +115,10 @@ With the additional `-v /home/user/galaxy_storage/:/export/` parameter, Docker w
115
115
116
116
This enables you to have different export folders for different sessions - means real separation of your different projects.
117
117
118
+
To detect when the Galaxy distribution in the image changes, the container writes a marker at
119
+
`/export/.galaxy_export_marker`. You can override the marker value with `GALAXY_EXPORT_MARKER` if you
120
+
need deterministic export refresh behavior.
121
+
118
122
You can also collect and store `/export/` data of Galaxy instances in a dedicated docker [Data volume Container](https://docs.docker.com/engine/userguide/dockervolumes/) created by:
119
123
120
124
```sh
@@ -517,7 +521,16 @@ This is achieved by connecting to Galaxy's CernVM filesystem (CVMFS) at `cvmfs-c
517
521
The CVMFS capability doesn't add to the size of the Docker image, but when running, CVMFS maintains
518
522
a cache to keep the most recently used data on the local disk.
519
523
520
-
*Note*: for CVMFS directories to be mounted-on-demand with `autofs`, you must launch Docker as `--privileged`
524
+
*Note*: for CVMFS directories to be mounted-on-demand with `autofs`, you must launch Docker as `--privileged`.
525
+
If privileged mode is not an option, use the optional CVMFS sidecar in `galaxy/docker-compose.yaml`:
526
+
527
+
```sh
528
+
cd galaxy
529
+
CVMFS_MOUNT_DIR=/cvmfs EXPORT_DIR=./export docker compose --profile cvmfs up
530
+
```
531
+
532
+
This starts a dedicated CVMFS container that mounts the repositories and shares `/cvmfs` with the Galaxy
533
+
container. The CVMFS cache is persisted in `${EXPORT_DIR}/cvmfs-cache`.
521
534
522
535
523
536
## Personalize your Galaxy <a name="Personalize-your-Galaxy" /> [[toc]](#toc)
@@ -748,6 +761,7 @@ When you execute the tool again, Galaxy will pull the image from Biocontainers (
748
761
| `LOAD_GALAXY_CONDITIONAL_DEPENDENCIES` | Installing optional dependencies into the Galaxy virtual environment |
749
762
| `LOAD_PYTHON_DEV_DEPENDENCIES` | Installation of Galaxy's dev dependencies. Needs `LOAD_GALAXY_CONDITIONAL_DEPENDENCIES` as well |
750
763
|`GALAXY_AUTO_UPDATE_DB`| Run the Galaxy database migration script during startup |
764
+
|`GALAXY_EXPORT_MARKER`| Override the export marker used to refresh `/export/galaxy`. |
751
765
752
766
753
767
# HTTPS Support <a name="HTTPS-Support"/> [[toc]](#toc)
0 commit comments