Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
tabo
Is this you? Claim Profile »
1 year ago
in django-galaxy: a reusable feed aggregator in Django - Officially Lucky, a blog by Clint Ecker on Officially Lucky
Nice, I'll definitely take a look on this.
Now about feedjack, I'd like to point that it is an _old_ piece of software that I hacked together in a weekend to teach myself django. It's so old that django sites wasn't documented (so I didn't use them) and django-taggin just didn't exist ;) I've been patching it to fix bugs and add minor features here and there, but the main design of the app still remains.
My short term plan is to do something like you just did. First write a new denormalized tagging app so the site doesn't rely so much on caching (count aggregates are NOT good for your DB), then a pluggable "do-what-I-want-with-feeds-and-apis" app (placeholder in http://code.google.com/p/pypipes/ ), and then a site that uses these apps. That's all in my short-term TODO, I just need some time ;)
And about feedjack not being optimal in plugging it to a site, well, it's true in the sense that the process isn't _documented_. I've helped a couple of users on doing that privately and it's really easy to do. Feedjack is, after all, a django app with public models and _lots_ of helpers to plug them in a existing site.
Anyway, I got my copy of Practical Django Projects yesterday. I'll read it as soon as I can, maybe I'm missing something :)
Now about feedjack, I'd like to point that it is an _old_ piece of software that I hacked together in a weekend to teach myself django. It's so old that django sites wasn't documented (so I didn't use them) and django-taggin just didn't exist ;) I've been patching it to fix bugs and add minor features here and there, but the main design of the app still remains.
My short term plan is to do something like you just did. First write a new denormalized tagging app so the site doesn't rely so much on caching (count aggregates are NOT good for your DB), then a pluggable "do-what-I-want-with-feeds-and-apis" app (placeholder in http://code.google.com/p/pypipes/ ), and then a site that uses these apps. That's all in my short-term TODO, I just need some time ;)
And about feedjack not being optimal in plugging it to a site, well, it's true in the sense that the process isn't _documented_. I've helped a couple of users on doing that privately and it's really easy to do. Feedjack is, after all, a django app with public models and _lots_ of helpers to plug them in a existing site.
Anyway, I got my copy of Practical Django Projects yesterday. I'll read it as soon as I can, maybe I'm missing something :)
1 reply
There's not nearly as much work put into my project as you've done
with yours. In fact I borrowed some ideas here and there from how you
processed entries out of Feedburner.
I didn't mean to say that your application behaved badly or anything,
and I did forget to mention that your application was written during
the dark ages of Django ;)
I just meant that there is a lot of stuff that's in there that's
duplicated and can be handled nicely using Django's built-in
facilities, mainly sites and caching. I've also always been a little
confused about the Feeds/Sites/Subscribers system you had going.
I wanted to see if I could build a bare bones aggregator with just
Blogs, Posts, and seeing if Django could do the rest. I'm hoping to
be able to convert over ArsLounge on a test site to see how well that
works!