Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitattributes

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions .gitignore

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions .prettierignore

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions .projen/files.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

26 changes: 25 additions & 1 deletion .projen/tasks.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

79 changes: 72 additions & 7 deletions API.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 5 additions & 3 deletions docs/application-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,11 @@ ConstructHub provides two package source implementations: `NpmJs` and
function is invoked, which stages the package tarball into an S3 bucket then
notifies the ConstructHub ingestion SQS queue. The CouchDB follower is
scheduled to run every `5 minutes`, and stores its state (receipts for the
change entries received, time/sequence checkpoints, and laggy packument
expectations) in a specific object in the S3 bucket used for staging package
tarballs.
change entries received, and time/sequence checkpoints) in a specific object
in the S3 bucket used for staging package tarballs.
When the registry serves an older revision of a package than the feed
announced, the package is sent to a queue, and a packument processor function
checks it again, with growing waits, for about a day.
The package versions it has processed are recorded in a DynamoDB table, so
each version is only processed once.
Existing deployments kept this list in the S3 bucket; it is copied to the
Expand Down
Loading
Loading