I write here because I want to understand if what I’m trying to do makes sense.
I’ve a small static website and I would like to publish on IPFS but I don’t like DNS (let’s suppose) ans so I would like to use only ENS without dnslink. At the moment I’ve the following automated workflow when I commit on my GitHub repository:
- The site is built
- It uploads it to Pinata using a GitHub action and get the CID hash
- It makes a POST to my personal IPFS node to pin the new version
- It makes another POST to my node to publish using IPNS
Now my site is reachable at a static IPNS hash, it’s a little slow the first time I visit it using a gateway (both the mine and that of Pinata) but it’s ok for my needs.
The first step would be to buy an ENS domain and link it to my IPNS hash, the reason because I can’t update the ENS record with a new CID every time is that I would need to make a Ethereum transaction and it costs.
Another thing because someone asks: the IPFS API is behind a Nginx proxy with the authentication enabled, so I’m the only that can update the IPNS address.
Last thing: I don’t like the idea to use a third party service, now I’m using Pinata only to increase the redundancy.
My major doubts are:
a. If my node shut down people can get my site knowing only my IPNS address?
b. I can set a
lifetime parameter with IPNS when I make
name/publish call, the default value is
24h, can I set something like
c. Could be useful set the
ttl value too?