W3C home > Mailing lists > Public > public-perma-id@w3.org > November 2014

Idea: Travis-like testing of .htaccess?

From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Date: Mon, 17 Nov 2014 14:25:47 +0000
Message-ID: <CAPRnXt=QR2yp9HyYdNRshZTR1g9NKFHZsTgCefP=8QTigtSXUQ@mail.gmail.com>
To: public-perma-id@w3.org
Hi, I recently messed up one of my .htaccess files and got a lovely 500 error..

https://github.com/perma-id/w3id.org/pull/58


Normally I test out the .htaccess file in a random folder on one of my
own servers - but this time I was just doing one of those quick edits
and messed up by adding a space.


Do you think it is possible to have some kind of automatic testing or
semi-automatic staging of a suggested .htaccess pull request? I'm kind
of Travis-CI which can run tests on any pull request and then comment
on the request with the test results.


Perhaps it could be something as simple as

cat $(find . -name README.md)  | grep https://w3id | sed s/cleverbithere//

and then try each of those to see that it gets redirected correctly
(and that the destination is not 404)?


Then we can recommend such a pattern to just include example links in
the README.md.




-- 
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Monday, 17 November 2014 14:26:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:35:47 UTC