Update publishing workflow instructions #1470
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why these changes are being introduced: We previously had to scale up Heroku dynos prior to running the publishing job. Now that APT handles the bagging of SIPS, this is no longer necessary. We have run two publishing jobs and have not yet seen a memory spike. Relevant ticket(s): * [ETD-669](https://mitlibraries.atlassian.net/browse/ETD-669) How this addresses that need: This removes the dyno scaling instructions from the readme. Side effects of this change: We've only done two publishing runs since integrating APT. It's possible that dyno scaling is still needed, and we just haven't encountered a problem thesis yet. This is highly unlikely, however, since creating bags was the most memory-intensive part of the publication process.
JPrevost
approved these changes
Sep 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why these changes are being introduced:
We previously had to scale up Heroku dynos prior to running the publishing job. Now that APT handles the bagging of SIPS, this is no longer necessary. We have run two publishing jobs and have not yet seen a memory spike.
Relevant ticket(s):
How this addresses that need:
This removes the dyno scaling instructions from the readme.
Side effects of this change:
We've only done two publishing runs since integrating APT. It's possible that dyno scaling is still needed, and we just haven't encountered a problem thesis yet. This is highly unlikely, however, since creating bags was the most memory-intensive part of the publication process.
Developer
our guide and
all issues introduced by these changes have been resolved or opened as new
issues (link to those issues in the Pull Request details above)
Code Reviewer
(not just this pull request message)
Requires database migrations?
NO
Includes new or updated dependencies?
NO