Skip to content

Conversation

@BryonLewis
Copy link
Collaborator

@BryonLewis BryonLewis commented Oct 29, 2025

Following the Girder 5 Upgrade

Using Migration Guide

ON HOLD: This is on hold until I get some way to propery set the girder plugins to utilize the /girder installation location.

TODO:

  • Tag new version of builds to girder-5
  • Update Environment Variables
    • WORKER_API_URL -> GIRDER_SETTING_WORKER_API_URL
    • CELERY_BROKER_URL -> GIRDER_WORKER_BROKER
    • Add GIRDER_WORKER_BACKEND
  • Remove RUN girder build and corresponding logic from the docker build process
  • replace all import logger from girder with import logging and configuration a logger
  • Update pyproject.toml dependencies to use girder-5 compatible versions of girder plugins
  • Specifically update the large-image pluging to use the girder 5 version
  • add the girder-worker-plugin and replace calls that were in girder_worker.girder_plugin to use girder_worker_plugin
  • Modify the __init__.py to configure the route for the DIVE Vue application interface.
  • Finalize the Girder Core build so it will build all plugins with the proper references to files. Currently plugins aren't properly referencing the /girder subpath
  • Update client code to use websockets vs the eventstream that was previously being used for notifications (may require overriding some GWC stuff
  • Testing conversion tasks
  • Testing Pipeline tasks
  • Testing training tasks.
  • Test import of S3/MinIO data and ensure it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants