It’s just data

Feed Validator setup howto

Joseph Walton: With the RSS Advisory Board recommending the Feed Validator, and highlighting that it’s an open source project (Python licence), here’s a simple starter for hacking on it, either to make fixes, or simply to use it for non-public feeds.

Cool!


I’ve checked it into the ‘howto’ directory. src/runtests.sh was my attempt at unifying all the tests. It runs everything, but there’s no consistent reporting of success or failure, which makes it far less useful.

I gave those locations for DOCSURL and CSSURL the ‘fv-’ prefix because they’re in the user’s account, rather than part of a top-level validation service. I think that change would clash with the current validator deployment in a top-level +ExecCGI directory, so I’ve left them for now.

Posted by Joe Walton at

I’ve checked it into the ‘howto’ directory. src/runtests.sh

Thanks!

I think that change would clash with the current validator deployment in a top-level +ExecCGI directory, so I’ve left them for now.

I was confused, but now that I have looked into it, I question why you needed to change this at all.

I do all my development using http://localhost/~rubys/feedvalidator/, and deploy to http://feedvalidator.org/.  In both cases, the existing relative URIs “just work”.

What problem are you seeing that led you to include instructions on how to change this into your howto?

Posted by Sam Ruby at

I still deploy with:

  <Directory /home/*/public_html/cgi-bin>
  Options +ExecCGI

and no ExecCGI outside cgi-bin, which is probably a bit of an anachronism. Your edit is a lot clearer though; thanks.

Posted by Joseph Walton at

(Update: The current version of these notes is now in the Feed Validator docs directory, updated to include the move to Subversion and with path setup much simplified by Sam.) With the RSS Advisory Board recommending the Feed Validator, and...

Excerpt from Kafsemo.org at

Add your comment