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

app: On publish store module metadata in DB #25

Closed
juliangruber opened this issue Feb 10, 2020 · 0 comments
Closed

app: On publish store module metadata in DB #25

juliangruber opened this issue Feb 10, 2020 · 0 comments
Assignees
Labels

Comments

@juliangruber
Copy link
Member

@juliangruber juliangruber commented Feb 10, 2020

When the CLI publishes a module, it only tells the vault the module's url. The vault will then fetch the module's metadata and insert module title, description, etc into the database. This is in order to prevent the CLI from inserting false information. Currently the worker is the only system with Dat access, and it might be good to keep it this way. So, after the module is published, a worker needs to pick up the module's key, fetch its meta and tell app about it, so it can update its db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.