-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
DNSLink and IPFS Pinning #2338
Comments
Also this sir: #1919 |
If I may, I added #1695 here since the approach seems like it would depend on having IPFS up. |
Jake offboarding notes and to do:
|
@ironoa Will Jakes cloudflare keys be an issue? Should we move the cloudflare account to a shared email and regenerate the apiKeys? |
Update for DNS chaining issue: ipfs/ipfs-companion#1039 (comment) |
@emresurmeli need to rotate IPFS credentials in 1Password again |
I am moving the completion of this work to an updated issue, #3651. I added a reference to this issue in the description to track all the previous knowledge. |
Hey @emresurmeli, do you happen to know which email address was used here? I was able to track down the cluster credentials in 1Password but the username listed isn't an email address and CloudFlare requires the email as the login. Maybe the credentials in 1Password aren't for CloudFlare? No worries if you're not sure just trying to track down what is existing vs what may need to be re-created. |
Based on this configuration it seems like the API key is stored in 1Password but not the login details for the account. |
Accessing the wikis via IPFS is really close to being possible.
Next steps
CICD Script
This will allow the wikis to be loaded with IPFS-compatable browsers at https://polkadot-wiki.w3f.services, https://kusama-guide.w3f.services. It is almost complete, just needs bugfixing at the DNS TXT updating that happens here.
Things to note while finishing this:
prod
branch (eg. here). There is no reason this can't change this to a test server.DNSLink chaining issue
This will allow the wikis to be loaded via IPFS-compatable browsers transparently through the main websites (eg. https://wiki.polkadot.network, https://guide.kusama.network)
These two things complete putting the wikis on IPFS with easy access.
Other Optimizations
There are a few optimizations we can do after this:
Setup
ipfs-cluster-follow
supportThis would make it really easy for anyone to join the cluster as a follower, replicating anything we pin to the wiki to their computer. This makes for higher data availability and quicker data accessibility. I think it could be really cool to turn this into a Polkadot/Kusama IPFS Cluster, pinning important things for the network, W3F, and Parity.
The text was updated successfully, but these errors were encountered: