-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
✨NNew feature or requestNew feature or request
Description
New Feature Summary
Back in June, we added a Brandeis specific file location resolution system that consists of
- add support for
document.locationresolver plugins mmif-python#222 - https://github.com/clamsproject/aapb-brandeis-datahousing
- https://github.com/clamsproject/mmif-docloc-baapb
But to utilize the new resolver server, app container should install the additional mmif-docloc-baapb plugin.
Also moving forward, I believe there will be more Brandeis-specific MMIF/CLAMS components added to the platform.
Hence, I'd like to make more container images pre-shipped with Brandeis specific components.
Issue will be done when
- container-related GHA-WF files are updated (https://github.com/clamsproject/clams-python/tree/87240378179d51ce9b3e73ff0c7cbaaecce63477/.github/workflows)
- if necessary, more containerfiles are added (https://github.com/clamsproject/clams-python/tree/87240378179d51ce9b3e73ff0c7cbaaecce63477/container)
- all new images are uploaded to our ghcr (https://github.com/orgs/clamsproject/packages)
Related
No response
Alternatives
Until these new images are added to our ghcr, devs can use something like this in debugging process to use the (WIP) resolver server.
podman run \
--rm \
--name <some-container-name> \
-e BAAPB_RESOLVER_ADDRESS=<resolver_server_name>.brandeis.edu:<resolver_server_port> \ # IMPORTANT: let docloc resovler to know where to query
-p <someport>:5000 \
-v /mnt:/mnt \
ghcr.io/clamsproject/<appimage-id>:<appimage-ver> \ # OR if you build a new image fro WIP codebase, use that name
/bin/bash -c 'pip3 install mmif-docloc-baapb && python3 /app/app.py' # IMPORTANT: swap default cmd with `pip install + app.py`
### Additional context
_No response_Metadata
Metadata
Assignees
Labels
✨NNew feature or requestNew feature or request
Type
Projects
Status
Todo