Autochecked users, Bureaucrats, Editors, oversight, recentchangescleanup, Reviewers, rollback, Administrators
19,746
edits
(a checklist (some items)) |
No edit summary |
||
Line 1: | Line 1: | ||
{{underconstruction}} | {{underconstruction}} | ||
These are the steps for setting up a new WikiIslam subdomain. | These are the steps for setting up a new WikiIslam subdomain. This can also be used for setting up the site on a new server. | ||
;Initial setup (Server access) | ;Initial setup (Server access) | ||
Line 24: | Line 24: | ||
;Checklist | ;Checklist | ||
This is a checklist for new website installations. | This is a checklist for new website installations. These checks take some time to complete so do the most important/simple checks first (e.g. page views) | ||
* New Server Setup: Typical Shared hosting will not work. Use a VPS instead. NGinx is strongly recommended for higher speed instead of Apache ([http://www.theorganicagency.com/apache-vs-nginx-performance-comparison/ Apache/NGinx comparison for a SQL/PHP setup]). Mediawiki is PHP/SQL based. Also use Mediawiki's own file cache and any other methods available. | |||
* Original URLs should work (or incoming links will be broken). For example [http://www.wikiislam.net/Allah http://www.wikiislam.net/Allah] should work]). Links can be broken after creating short URLs with htaccess, rewrite or other methods. So if the new URL is http://www.wikiislam.net/index.php?Allah or something like that, this will result in incoming broken links. | * Original URLs should work (or incoming links will be broken). For example [http://www.wikiislam.net/Allah http://www.wikiislam.net/Allah] should work]). Links can be broken after creating short URLs with htaccess, rewrite or other methods. So if the new URL is http://www.wikiislam.net/index.php?Allah or something like that, this will result in incoming broken links. | ||
* Images: Check pages which have images and see if images show up. Later also check if an image can be resized. | |||
* Images: Check pages which have images | |||
* Email functions work: Enable emailing on an account and send a test email using the "email user" function (accessible on the left for a user who has email enabled) | * Email functions work: Enable emailing on an account and send a test email using the "email user" function (accessible on the left for a user who has email enabled) | ||
* Links to sub-domain articles work | * Links to sub-domain articles work | ||
Line 33: | Line 33: | ||
* Main domain redirects work (should redirect to the main page) | * Main domain redirects work (should redirect to the main page) | ||
* Page editing works. Use test pages. | * Page editing works. Use test pages. | ||
* Anti-spam works. New account and anonymous edits should require a Captcha that works effectively for bots. ConfirmEdit's Questy Captcha is one of the best options. | * Anti-spam and anti-vandalism: | ||
* Anti-vandalism features work (use extension AbuseFilter or other anti-vandalism methods). | |||
* Until the above two features work, user account registration and anonymous edits should be disabled. | ** Anti-spam works. New account and anonymous edits should require a Captcha that works effectively for bots. ConfirmEdit's Questy Captcha is one of the best options. | ||
** Anti-vandalism features work (use extension AbuseFilter or other anti-vandalism methods). | |||
** Until the above two features work, user account registration and anonymous edits should be disabled. | |||
* If time permits, check for issues in different browsers (Chrome, Firefox etc) and platforms (PC, Mobile, MAC). At the least check if a page can be viewed in a browser or platform. | |||
* Login/Logout works. Check a few page views in both logged out and logged-in states. | |||
* Check for server load. High traffic can be around 6-10 times the normal traffic. The server should still be able to work quickly without excessive CPU or swap usage. |
edits