[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Database migration: display a 503 message

This looks really helpful - would it make sense to concatenate the html around repository config?  I should think people already have the repository name and contact email in the config, and would be more sustainable?

I'll try and give it a whirl on my test environment this week.


Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2015)
Technical Data Officer
The Library 4.10, University of Bath, Bath, BA2 7AY UK
Ext. 3570 (External 01225 383570)
E.Jennings at bath.ac.uk
Research Data Management: http://www.bath.ac.uk/research/data

-----Original Message-----
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of John Salter
Sent: 14 March 2016 16:34
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Database migration: display a 503 message

I've been doing a bit of database migration today (between mysql versions more than 2 major releases apart - so I couldn't just setup a replication).

I've written some instructions about how to make a repository respond with a 503 (Service unavailable) status, and show a human-friendly message at the same time:

If anyone wants to review it / comment on it, please do.
It seems to work OK on 3.3.10 - and I can't see why it wouldn't work OK on other versions.
The main question I have is how Apache versions might change the code needed to allow a certain IP through. Any thoughts on this welcome!


*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/