What our engineers handle on MediaWiki
This is the hands-on work, done by a person: the jobs the automatic tools cannot do for you.
- 1Tune PHP, the database and caches such as Memcached or Redis
- 2Make sure the job queue runs by cron so updates and links stay current
- 3Upgrade MediaWiki and extensions on a copy first
- 4Back up the database and uploaded files, and test a restore
Problems we fix
Problem
The wiki is slow when pages are edited
What we do
We check job queue settings, caching and the database, and move jobs to cron.
Problem
Spam pages and fake accounts appear
What we do
We add captcha or account approval, block abusive networks and clean what was created.
Problem
An upgrade breaks an extension
What we do
We find the compatible version or remove the extension, run update.php and verify the pages.
Automatic tools, and our team for the rest
RootManage is automatic server management with every tool in one place. The tools run by themselves on a schedule and report to one dashboard. Everything they cannot do, and every emergency, is handled by our engineers by hand.
Automatic
RootManage tools, running by themselves
- Server Health agent reports load, disk use and failed login attempts to your dashboard.
- Uptime checks check the server every minute and email you when it stops answering, and again when it recovers.
- LiteHouse runs a low-priority audit of your website at 04:00 IST and lists findings you can act on.
- Site Clean scans nightly at 03:00 IST for phishing pages, spam scripts and webshells, with suspend, quarantine or delete actions.
- Backup agent runs scheduled backups at 02:00 IST to storage we provide or to your own SFTP or S3 box, with help restoring.
Manual, by our engineers
Everything else, and every emergency
- Hands-on work. Fixes, tuning, migrations, upgrades and the other jobs listed above on this page.
- Emergency work. A hacked site, an outage or a failed update is handled by a person who investigates and fixes it, not by a script.
- Things we do not automate. Anything the tools do not cover is done by hand, over SSH, WHM or RDP, on a login you can remove at any time.
The tools are optional, run on Linux servers and are installed by you with one command each. Every job our team does is recorded as a task in your dashboard with the details, and you get an email when it is updated.
How it works
- 1
Sign up
Create an account, choose a plan and add the server you want managed.
- 2
Install the tools
Run one command per tool. They then work by themselves and report to your dashboard. For hands-on work you give us a login you can remove at any time.
- 3
Automatic, with people behind it
The tools watch, scan and back up automatically and alert you. Our engineers do the rest by hand and handle every emergency, and you follow each task in your dashboard.
Questions about MediaWiki
Can you set up a private company wiki?
Yes. We configure login requirements, permissions and backups, and put it behind your SSO or VPN if needed.
Do you migrate wikis between servers?
Yes. We move the database and files, test and then switch DNS.
What does it cost to have MediaWiki managed?
Managed plans start at ₹1,999 a month for one server, and MediaWiki is managed as part of the server. The pricing page lists what each plan includes. If a server is already infected, the emergency cleanup is a one-time ₹9,000 job.