Pingly – a Roxen module for automatic Twingly pinging
Twingly is a blog search engine that focus on indexing the “blogosphere” rather than being a generic search engine. Twingly has a ping service that let you ping Twingly when you have new content on your blog so that Twingly can head over there and index the new content asap.
Since Roxen CMS have event hooks this module listens for newly published files and when found automatically notifies Twingly about it.
The only thing needed is to set up a config file in the SiteBuilder’s workarea so that this module knows under which paths newly published content should notify Twingly and with which arguments. But all this is documented in the module.
One note! If you run a replicated environment install this module on one of the frontend servers, not the backend. If installed on a backend Twingly might head over to your site before the new content has been replicated.
Oh, please ping frisim.com/ping/ at the same time. Frisim is the other (second
) famous Linköping-site to index blogs and news.
/Clas
Hey!
I tried to fix a module for Bonnier that the ping did not work on. Your experience seems to be that twingly is a bit quicker than the replicate system. Doh! I should have thought of that.
It seems the Twingly bot is there sniffing almost immediately and on our system the replication can be delayed 15-20 minutes. So I’ve installed this module on only ONE of the frontend servers.
Now, we have two frontends so it could happen that the server with this module gets its replication before the other server and that the Twingly bot gets sent to the other server, but I find that unlikely.
In this module I also have a delay (call_out(…)), so when the replication is caught in the event hook the call to Twingly isn’t done immediately. It would perhaps be a good idea to make this delay configurable so like: When the replication occurs wait 10 minutes and then call Twingly. This would probably be enough to make sure all frontends have been updated.
// Pontus