Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update metadata records based on ActivityPub server push #15

Open
2 tasks
pombredanne opened this issue Dec 13, 2023 · 0 comments
Open
2 tasks

Update metadata records based on ActivityPub server push #15

pombredanne opened this issue Dec 13, 2023 · 0 comments

Comments

@pombredanne
Copy link
Member

In a decentralized scenario, there are two or more servers cooperating. Here I would like to start building this multiserver architecture. Specifically, we should build an application to run in a second VulnerableCode and/or PurlDB server that can receive updates notifications from the FederatedCode ActivityPub server for a package and then fetch the data from the backing git stores. And use this to update this separate VulnerableCode and/or PurlDB instance, including minimally reconciling conflicts.
This could include:

  • Create the function(s)/services to receive updates notifications from the FederatedCode ActivityPub server in VulnerableCode and/or PurlDB
  • Create script(s) to fetch the backing data from the corresponding FederatedCode backing Git repository and update the local records in VulnerableCode and/or PurlDB, reconciling conflicts as needed
@pombredanne pombredanne transferred this issue from aboutcode-org/purldb Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant