I’m pretty sure IPNS is the only way to have an actual fixed and unchanging CID which you can update the content under, and so that’s the place to look. For your use case of an updated website it might not be a problem that there’s one limitation with IPNS which is that it can take like up to 3 to 5 minutes (or longer?) to republish (update) with new content, because it has to transmit out the new name similar to what DNS does.
FWIW I currently run my website from home (it’s a smattering of random things while I toy with IPFS http://portal.thedisco.zone). I keep IPFS/IPNS using ipfs-sync, which will look at a directory, copy the contents to MFS, pin it, and update an IPNS key whenever it detects a change.
Like wclayf pointed out though, it can take a couple mins sometimes to actually see the changes reflected. However, I don’t mind.
I don’t think hardware requirements are super strict. I hear about some success running on Raspberry Pis. I personally run on my desktop computer, but I don’t power it off.
@Discordian I like what you did there! I’m just now learning GO so I can’t scrutinize it much, but I think I get it, and if there are no plans to build this capability into MFS already, I hope the IPFS developers find it and help you finish it, or see if it or something like it can become part of MFS as a ‘sync’ command.
There’s huge demand in the IPFS world for a way to sync to MFS. You may have already searched around on this forum and found that out. There have been several discussions about this kind of thing. Nice work, and thanks for sharing it here.