First of all my no-backend CMS apparently isn’t possible yet, because:
IPFS in browsers have very limited (essentially no) access to the IPFS network.
Yeah, that is an issue that brings an immediate halt to this project. Bummer ![]()
You’re right. There is.
In my future CMS, there will be a Submit button somewhere. In its onClick event handler call-back, I’ll need to do the equivalent of:
ipfs add -r website/ipfs name publish /ipfs/$hash
Whether the phrase “IPNS pinning” includes item 1 or not doesn’t really matter to me, since I already know how to accomplish item 1. For what its worth I thought of it as only meaning item 2.
But I’d also want it to be a remote service so that the js-ipfs node can terminate shortly after 2 has been completed, so that the user can close the web browser.
But it all doesn’t matter if I have to have a backend anyway. I was hoping that js-ipfs was all the backend I was going to need.