Hi, I don't follow OG development but as host operator a few things are
coming up. The machine's load is gradually climbing over time and some
of that is OG.
Despite a relatively low hit rate on OG it is consuming quite a bit of
resource. If OG started taking off it would take the machine down.
First up: index.cgi requires 0.35s to perform a `perl -c` syntax check.
Any thoughts on putting OG on a mod_perl server? I have mod_perl running
here of course and we'd need to coordinate some apache.conf stuff.
Second: the supersearch.cgi gulps down CPU, often for seconds at a time.
It is a frequent resident of `top` output. This isn't really
acceptable. I'm going to request this feature be turned off unless an
effective optimisation plan or some other way to reduce its impact
here is constructed pretty soon. Sorry about this but it's encroaching
on others.
Third: I wonder if there's some way to instruct robots not to spider
parts of your wiki. This ought to speak for itself:
$ grep crawl /var/log/apache/london.openguides.org-access.log | grep 'action=edit' | wc -l
8242
$
Finally: I posted about a DoS and was wondering what the status of a
solution was. http://openguides.org/mail/openguides-dev/2004-October/000542.html
Cheers,
Paul (any overbearing tone unintentional ;-)
--
Paul Makepeace .............................. http://paulm.com/inchoate/
"If my elbow was straight, then I'll show oyu mine!"
-- http://paulm.com/toys/surrealism/
Hi,
I'd done some patching to St. Paul and wanted to feed hte changes back. Tickets #154 and #155 in the Trac (http://dev.openguides.org) are both from work I'd done previously with St. Paul's guide.
#154 provides basic JSON support for nodes and indexes. The Wiki::Toolkit::Plugin::JSON uses either JSON.pm or JSON::Syck to produce the output.
#155 provides a 404 script for when things go away. St. Paul had some problems with incosistant URLs in the past and I noticed that 404s were very large because of this, so I wrote a little CGI to try to help you can see it in action by going to http://saintpaul.openguides.org/Pino's_Pizza ... it will suggest the right URL for the guide, or possibly a Search. I've cleaned up the script so that it does everything in a generic fashion and should integreate cleaner with other people's templates etc. (Originally I was just dumping HTML but I went and made a template now.)
I hope people find these useful. :)
-Chris
Eventually...
Thanks largely to the good work done by all at the Oxford meetup, we
have a fair number of bugfixes and new features available as 0.58.
Grab it from CPAN, or directly from
http://www.larted.org.uk/~dom/computing/code/openguides/OpenGuides-0.58.tar…
or from Debian unstable[1][2].
Changelog follows:
0.58 21 December 2006
Tidy up some minor bugs in the new features.
Add RDF autodiscovery link to nodes' <head> section.
Added more data to RDF output
Redesign node history view along lines of that used by MediaWiki
(http://www.mediawiki.org/) for clarity.
Add UPGRADING file which summarises important information for people
upgrading.
Add an optional new config parameter, http_charset, which will set
an explicit charset http header on all responses.
Add an optional new config parameter, ping_services, which is a list
of services (defined in Wiki::Toolkit::Plugin::Ping) to ping when
a node is written. Allows you to ping pingerati etc on changes.
Helmert Transforms, so that British National grid users can have
accurate Google Maps tie-ins.
dbencoding config variable to tell OpenGuides what charset your
database encoding is.
As a consequence declare the charset correctly in the XML feeds.
Other minor UI improvements
Redesigned node history view a la MediaWiki for greater clarity.
Cheers,
Dominic.
[1] after the next mirror pulse
[2] but beware. It's not currently installable from unstable, because the
libtemplate-perl package needs updating in Debian (which I am working
on).
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
Hi!
Just a minor note with the OpenGuides home page
http://openguides.org/
it lacks the "background-color" attribute of the body element in its css
http://openguides.org/openguides.css
while the site seems to be designed to have a white background.
Without the background-color attribute in the css (or the "bgcolor"
attribute in the HTML, which is however deprecated) the user, when he
visits the site, sees the default background color he has set in his
browser, which could be different from "White" (mine is a shade of gray
for example), so that the result can be quite dusturbing.
If you have not experimented this, it's only because you browser's
default background color is set to "White" (which is the default choice
for many browsers, but the user can easily change it).
Thank you for your great work with OpenGuides!
Cheers,
Emanuele Zeppieri.
We've had some issues with Text::WikiFormat in the last few months and
it doesn't seem to get updated very often. As I commented during last
weekend's meetup, I'd like to replace it. HTML::WikiConverter looks
like a good possibility:
http://search.cpan.org/~diberri/HTML-WikiConverter-0.61/
It allows custom dialects to be implemented easily, so we wouldn't
have to worry much about our specific syntax (which is pretty much a
UseModWiki subset anyway).
Thoughts?
--
Earle Martin
http://downlode.org/http://purl.org/net/earlemartin/
> -----Original Message-----
> From: openguides-dev-bounces(a)lists.openguides.org
> [mailto:openguides-dev-bounces@lists.openguides.org]On Behalf Of Earle
> Martin
> Sent: 14 December 2006 11:17
> To: OpenGuides software developers' list
> Subject: [OGDev] Alternatives to Text::WikiFormat
>
>
> We've had some issues with Text::WikiFormat in the last few months and
> it doesn't seem to get updated very often. As I commented during last
> weekend's meetup, I'd like to replace it. HTML::WikiConverter looks
> like a good possibility:
>
> http://search.cpan.org/~diberri/HTML-WikiConverter-0.61/
>
> It allows custom dialects to be implemented easily, so we wouldn't
> have to worry much about our specific syntax (which is pretty much a
> UseModWiki subset anyway).
>
> Thoughts?
>
Can we go for a generic approach. Like the wiki store being a pluggable back end, I see the formatter as something similar.
As far as I am aware, OpenGuides and Wiki::Toolkit have been architected this way.
Maybe the formatter can be a config choice.
the edit conflict template doesnt have everything that you can edit from
edit_form.tt
--
Bob Walker
http://www.randomness.org.uk/
Stress Kittens: Squeeze them till they cry!
The latest tech in homicidal tendency relief.
I will release OpenGuides 0.58 by the end of the week. Developers:
please let me know if you have active work going on and have things that
you think will be ready for it so I can plan accordingly.
Dominic.
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
Hi all,
Apologies it took me so long to pick up this thread. Slightly later
than planned, here goes:
Background: there seems to be some enthusiasm for supporting
reviews/ratings on the OpenGuides, both of articles, and the things
the articles are about (ie. "Rate this article about the Red Lion Pub"
and "Rate the Red Lion Pub").
Issues: is it worth developing Yet Another Reviewing and Rating
Infrastructure, specifically for the OpenGuides?
Potential Solution: I have developed Revyu.com <http://revyu.com/>, a
site that acts as a generic platform for creating reviews and ratings
of things (anything at all), on the basis that people can easily get
reviews and ratings back in RDF/XML (via simple GET requests or SPARQL
[1] queries) for reuse in their own applications.
In the context of the OpenGuides, it would be pretty trivial to
provide "Review/Rate this article about the Red Lion" and "Review/Rate
the Red Lion" links on OpenGuides pages, that pass the user to
Revyu.com to provide the review, then sends them back to the OpenGuide
page afterwards, very much like the way "add this to del.icio.us"
links work on sites like The Register. SPARQL queries from the
OpenGuides sites could then retrieve all reviews related to a
particular page, from Revyu.com, and present the results as desired.
This approach has some nice advantages: it doesn't require changes or
additions to underlying database structures, creation of new reviewing
forms or scripts to do RDF output of reviews (this is all provided by
Revyu), and may help the OpenGuides reach new audiences as content
would show up on other sites. It would also serve as a nice
demonstration of the power of doing things Semantic Web-style, and how
amenable Open Guides are to this. Disadvantages are few IMHO, mainly
that it would require SPARQL support to be added to the OpenGuides at
some level. On the upside, I think there are decent Perl libraries for
SPARQL, and it is a fun thing to learn. As an interim solution we
could always use iframes or some other method to show content from
Revyu on the OpenGuides.
So, what do people think? Is this something people would be interested
in doing? Please fire back any questions, or check out the site
<http://revyu.com/>, or both. Anyone going to Oxford tonight for the
Hackfest will probably be lucky enough to get a demo ;)
Looking forward to hearing thoughts, comments, etc.
Cheers,
Tom.
[1] This is a nice intro to SPARQL:
http://www-128.ibm.com/developerworks/xml/library/j-sparql/
On 05/11/06, Tom Heath <tom.heath(a)gmail.com> wrote:
> Hey people,
>
> A big fat yes to all those questions :) I'm just about to launch a
> service for reviewing and rating things, done semantic web style so
> all the output is in RDF/XML and can be integrated into other sites.
> It would be great if we could deliver reviews and ratings to the
> OpenGuides using this as a backend, rather than reimplementing a load
> of the same functionality. I'm away now for a few days but will write
> more when back later this week and have links to share.
>
> Cheers,
>
> Tom.
>
> On 04/11/06, Markus Linke <markus.linke(a)linke.de> wrote:
> > True, that would be quite nice!
> >
> > ----- Adam Auden <adam(a)bimble.net> wrote:
> > | On 11/3/06, Markus Linke <markus.linke(a)linke.de> wrote:
> >
> >
> > | On that note, perhaps a rating for the article too, a la Amazon's
> > | "Was
> > | this review helpful to you?" as well?
> > |
> > | A.
> >
> >
> > --
> > OpenGuides-Dev mailing list - OpenGuides-Dev(a)lists.openguides.org
> > http://lists.openguides.org/cgi-bin/mailman/listinfo/openguides-dev
> >
>