I’ve been trying to get my website on IPFS. I tried almost two years ago, and it looks like some things have gotten better in the meantime. However, the same thing that didn’t make sense before still doesn’t make sense.
Like most websites - like, for example, this forum - my website (macwright.org) uses absolute links. Hopefully it goes without saying that absolute links are very useful, and that changing them to relative links is not at all an easy workaround.
Unfortunately, given the way that the localhost:8080 gateway works, and the ipfs.io gateway, absolute links don’t work. If you try to rehost a website using them onto IPFS, all the absolute links will yank out the
/ipns/... bit of the URL and replace it with just the linked path.
It looks like ipfs.io itself uses relative links, probably to work around this limitation. I can’t find anything in the documentation about IPFS for websites about this problem.
Any ideas? This is limitation breaks most most websites, so even if it isn’t fixable, it should probably be mentioned in the documentation so that similar folks don’t go through steps 1-9 just to get blocked by step 10.