Using IPFS with your website
Though it is not required, it is strongly recommended that websites hosted on IPFS use only relative links, unless linking to a different domain. This is because data can be accessed in many different (but ultimately equivalent) ways:
- From your custom domain:
https://ipfs.tech/index.html
- From a gateway:
https://cloudflare-ipfs.com/ipns/ipfs.tech/index.html
- By immutable hash:
https://cloudflare-ipfs.com/ipfs/QmNksJqvwHzNtAtYZVqFZFfdCVciY4ojTU2oFZQSFG9U7B/index.html
Using only relative links within a web application supports all of these at once, and gives the most flexibility to the user. The exact method for switching to relative links, if you do not use them already, depends on the framework you use.
These popular JavaScript frameworks are covered in a blog post ↗ from Pinata ↗. They are fixed with minor config changes.
Gatsby is a JavaScript framework based on React. There is a plugin ↗ for it that ensures links are relative.
Add a file _includes/base.html
with the contents:
This snippet computes the relative path back to the root of the website from the current page. Update any pages that need to link to the root by adding this at the top:
This snippet also prefixing any links with {{base}}
. So for example, we would change
href="/css/main.css"
to be href="{{base}}/css/main.css"
For other frameworks, or if a framework was not used, there’s a script called make-relative ↗ that will parse the HTML of a website and automatically rewrite links and images to be relative.