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
* From the root of a local checkout of `dspace-submission-service`
380
+
* Python dependencies do *not* need to be installed
381
+
* Authenticate your terminal to appropriate AWS account and role (dssManagement)
382
+
*`make run-prod` (or `make run-stage`)
379
383
4. ETD processes output queue to update records and send email to stakeholders with summary data and list
380
384
of any error records. As of now this is a manual process, but can be triggered via rake task using the following heroku-cli command:
381
385
386
+
> [!IMPORTANT]
387
+
> Check the AWS Console to ensure the APT Lambda is active (i.e. not inactive) before proceeding. If you do not, the preservation jobs may fail if they have not run for a few days.
388
+
382
389
```shell
383
390
# run the output queue processing job
384
391
heroku run rails dss:process_output_queue --app TARGET-HEROKU-APP
@@ -397,7 +404,7 @@ You can publish a single thesis that is already in `Publication review` or `Pend
397
404
task:
398
405
399
406
```shell
400
-
heroku run -s standard-2x rails dss:publish_thesis_by_id[THESIS_ID] --app TARGET-HEROKU-APP
407
+
heroku run rails dss:publish_thesis_by_id[THESIS_ID] --app TARGET-HEROKU-APP
401
408
```
402
409
403
410
Note: `Pending publication` is allowed here, but not expected to be a normal occurence, to handle the edge case of the app thinking data was sent to SQS but the data not arriving for any reason.
0 commit comments