Difference between revisions of "Town Hall"
From Ancient Anguish Mud Wiki - AAwiki
(Caching: Important information for Editors) |
|||
| Line 1: | Line 1: | ||
'''This article is for random talks about administration, maintenance, structure, etc. Please create new topics with the headline markers '==' and everyone please remember sign topics and subsequent replies.''' | '''This article is for random talks about administration, maintenance, structure, etc. Please create new topics with the headline markers '==' and everyone please remember sign topics and subsequent replies.''' | ||
| + | |||
| + | Editors and Contributors can use the '''[https://aawiki.net/w2/index.php?title=Town_Hall&action=chat Town Hall WebChat]'''. You must be logged in to use it. At some point AAWiki Editor and Contributor meetings might be held in this chat. | ||
= Caching = | = Caching = | ||
Revision as of 04:42, 3 March 2014
This article is for random talks about administration, maintenance, structure, etc. Please create new topics with the headline markers '==' and everyone please remember sign topics and subsequent replies.
Editors and Contributors can use the Town Hall WebChat. You must be logged in to use it. At some point AAWiki Editor and Contributor meetings might be held in this chat.
Caching
The slow website response lately has been caused by DDOS (Distributed denial of service) attacks. If it was directed towards aawiki.net specifically is not known yet. I am hoping it was random (and that AA for dummies hacking attempts also are random) otherwise someone have something against AA. To faster and better serve pages, even if the database is offline or overloaded, I have enabled file caching. This creates normal HTML files out of every page and display these instead when anonymous users are viewing the page. It should not be noticeable in any way.
Now.. When you edit a page, the cache should purge itself automatically and recompile next time some anonymous user visits it. I've done a few tests and it seems this works. As long as you are logged in as editor, you will see the fresh page, not the cached version. If after you have done an edit, log out and notice the page you get served does not reflect these changes, you can log back in and you will find a 'Purge' option under 'More actions'. This will manually purge the page.
Again this should not be necessary, but if you have to manually purge pages let me know. Hopefully this will make the website a lot more responsive. --Admin (talk) 23:52, 1 December 2013 (CST)