Skip to content
Business Agile
← Work
Web · Online press, daily news · Mar 2017

Quotidien Libre

A daily paper throttled by its host, migrated then maintained every month.

Key figures

requests in eleven hours, on 28 November 201718,736
consecutive months of maintenance billed10
switchover window announced to the client45 min

Quotidien Libre is an online daily published by FG Éditions, of which Fabrice GIL is the founder, director and editor in chief. The site was growing, and that was precisely the problem: its shared host was throttling it, mainly through a cap on the number of queries allowed against the database. For a news site, where every article page triggers a series of queries, that cap is a wall. The provider's handling of the issue had not kept up.

The project in detail

The figures give the measure of what the site was taking. The access log of 28 November 2017, found in the archives, carries 18,736 requests over the first eleven hours of the day. That is the volume of a living press site, and it is not what an entry-level shared plan supports.

The migration was split into stages, so the impact on the business could be measured in advance and kept as short as possible. First an exact copy of the site in its new environment, then thorough testing with the client, because a migration reveals departures from coding standards and it is better to find them before switching. Then an agreed window during which the newsroom stops publishing, long enough to change the DNS records and wait for them to propagate. That step is the only constraining one, and I announced it as such with its estimated duration, rather than promising an invisible switch.

Application maintenance followed, monthly: database backups, updates of the WordPress core, the theme and the active plugins to their latest stable versions, and preventive measures when they were needed. For a daily paper the value of that contract is not technical but editorial: the newsroom stops looking after its infrastructure and concentrates on what it publishes.

The site ran on WordPress 4.9 with performance tooling consistent with its use: bundling and slimming of style and script files, image compression on upload, regular page speed measurement, a cookie consent banner and a search plugin. The recovered repository keeps the trace of the move: a diagnostic file left by the previous host was still sitting at the root, which is exactly the kind of residue a takeover has to clean out.

The relationship ran for ten consecutive months of invoicing, which is the only proof that counts for a maintenance contract.

What was done

  1. 01

    18,736 requests in eleven hours, measured in the access log

  2. 02

    The previous host's query cap identified as the cause

  3. 03

    Staged migration, with the outage window announced and costed

  4. 04

    Testing run with the client before the DNS switch

  5. 05

    Monthly maintenance: backups, updates, preventive work

  6. 06

    Diagnostic residue from the previous host found and cleaned out

Frequently asked questions

How do you know that hosting is throttling a site?

By looking at the logs rather than at impressions. On Quotidien Libre the host capped the number of database queries, and a single day's log carries 18,736 requests over eleven hours: the volume simply exceeded what the plan allowed.

Can a site migration happen with no downtime?

Not entirely, and I would rather say so. Changing the DNS records forces a window during which publishing has to stop. On Quotidien Libre that window was announced with its estimated duration before being committed to, and the newsroom could plan around it.

What does a maintenance contract give a newsroom?

Time. Backups, core, theme and plugin updates, preventive measures: none of it stays the newsroom's problem. On Quotidien Libre that contract ran for ten consecutive months.

Other work

A project? Let's talk this week.

A short brief, an answer within 48 hours, a firm estimate after scoping.

Describe my project