Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Invoke rake task in the (app? sidekick?) docker container to load ETD #8

Open
kerchner opened this issue Nov 5, 2023 · 0 comments
Open
Assignees

Comments

@kerchner
Copy link
Member

kerchner commented Nov 5, 2023

This is a first step and likely a temporary one. Ultimately this app is likely to be rewritten to create Bulkrax zip files (also with possible Ruby rewrite as per work started on the ruby-refactor branch).

Work for this ticket is to:

  • Rewrite the --import command so that instead of constructing and calling a rake command for each ETD, it constructs and calls commands to:
    • docker cp files for each ETD into the container (for example, to /opt/scholarspace/scholarspace-tmp or as configured)
    • docker exec to invoke the existing rake command inside the container to import this ETD
    • Remove the ETD files within the container

There should also be a way to monitor for success/failure of each upload as it occurs within the container, with log and/or stdout/stderr messages.

The role of sidekiq in this process should also be clarified. If we invoke the rake task in the app container, does the app send these jobs to the sidekiq queue? And/or should the rake task be called in the sidekiq container? Work on this ticket should clarify these questions -- but ultimately we will likely want this app to create a Bulkrax zip and load it through the Bulkrax API/CLI

@kerchner kerchner self-assigned this Nov 5, 2023
@kerchner kerchner changed the title Update to work with dockerized deployment of the app Invoke rake task in the dockerized deployment of the app Nov 5, 2023
@kerchner kerchner changed the title Invoke rake task in the dockerized deployment of the app Invoke rake task in the (app? sidekick?) docker container to load ETD Nov 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant