We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As follow up from #4 , we need to look into integrating service DID (currently hardcoded) with secrets and environments.
See https://github.com/web3-storage/upload-api/blob/17e1fdf7b7c5b5a40f3ed207cbf75f57aeea88a4/api/authority.js
We can take inspiration from authority.js + config.js in w3up repo
The text was updated successfully, but these errors were encountered:
SST supports Secret managment via SSM now, with a nicer api so i'm gonna use that https://docs.sst.dev/config
Sorry, something went wrong.
the base64 encoded edsigner private+public keypair is called:
PRIVATE_KEY
prod/uploads_v2/ingestion_service_key
SST.Config
e29dfe3
olizilla
Successfully merging a pull request may close this issue.
As follow up from #4 , we need to look into integrating service DID (currently hardcoded) with secrets and environments.
See https://github.com/web3-storage/upload-api/blob/17e1fdf7b7c5b5a40f3ed207cbf75f57aeea88a4/api/authority.js
We can take inspiration from authority.js + config.js in w3up repo
The text was updated successfully, but these errors were encountered: