Talk:September 2019 Outage Emails
|Thread title||Replies||Last modified|
|Let's discuss here||2||02:04, 21 October 2019|
There are some emails not in this archive: David Alves' tickets/emails to the hosting provider, Fnl's first emails regarding the outage, and any emails between admins that I wasn't a recipient of. For the sake of documentation, if you have a copy of those and are fine with making them public, please add them to the page.
Thank a lot for watching over the wiki and updating us on the situation.
I would suggest to bite a bullet and move away from mediawiki based wiki for the following reasons:
- we tied down to the hosting, if it goes down we cannot even have a workable read only mirror or a branch.
- if we lose access to the database dump, the game is over. It was OK 10 years ago but now it is somewhat shameful.q
- the only known way to me to make a copy of the wiki is via mediawiki dump, it is not incremental and pulls about a GB of data. So I run it only once a year after the outage event. I have no clue how to convert this dump back to a working web site :( But at least I can look at the pages when wikk is offline.
- this wiki has very low activity so it could be static. Mediawiki seems to be demanding to CPU so moving to the cloud with a meetered CPU is a bad option.
I would suggest ikiwiki as replacement.
- It is Git based (or some other choices of version control systems)
so we can have mirrors.
- Relatively non main stream so spammers attacks are more seldom.
- It generates static pages so very little CPU use, but have some macroses if we need something dynamic.
- A potential downside it looks quite old school design wise. Though, I personally see it as a plus.
We might even pay for the brancheble hosting, which takes care of hosting and backups of ikiwiki based wikis. It is ran by ikiwiki author Joey Hess.
When we had the last big downtime about a year ago, I attempted to convert wiki to git with git-mediawiki utility and had quite a success with main pages, I did not do well with discussions (but I did not try hard to do so).
I am willing to contribute my time towards the move or anything else which community find appropriate.
Great to see the discussions
I would say no service is overpriced, you either pay for more guarantee, or pay your precious time to do that yourself.
If you don’t want to handle all the hard things yourself, use AWS like cloud service, and robowiki is even suited for free tire for some of them.
If we want cheap VPS, then don’t forget to setup backups to many other data storage yourself. VPS failure causing data lost is common, and our data is more valuable than the price of the cheapest VPS I think.