-
Notifications
You must be signed in to change notification settings - Fork 7
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
IPNS support #4
Comments
This action does the work by sending the content to a remote ipfs-cluster. This was deliberate so we offload the IPFS work to a long running node. Setting a DNSLink or updating an IPNS record could be seperate action / entrypoint. Ideally you'd just do it by exposing a pinning api on a remote node behind basic auth or similar. 💁♂️ |
of course by pinning i mean ipnsing. |
For completeness, it's worth noting that this action does not handle setting dnslinks, but it does provide the CID as an output, so you can pass it to dnslink or IPNS setting step like https://github.com/filecoin-project/specs/blob/71f37208a1f4f56b33ea307d7cbdb4b06996b115/.github/workflows/main.yml#L38-L44 |
Ack, makes sense 👍 Should we keep this issue open until we have an established way of doing IPNS updates on CI? Eg. a separate action. |
Would be really useful to update IPNS record in addition to updating DNSLink. Or instead.
This requires figuring out how key management should work in CI contexts. Would entire publishing key be a secret defined in settings of a GitHub repo and passed to the action?
@olizilla any prior art or thoughts about his?
The text was updated successfully, but these errors were encountered: