Nice looking project, here. This is very much the same as what I do on jeffcroft.com, but it’d a bit more lightweight and the importers are probably better-written (I’m still not a great programer!). My stuff will be open-sourced at some point — but it’s good to have options, and this is available now.
001 // Keri Henare // 04.21.2008 // 12:28 PM
I found this recently too thanks to Django Plugables. It’s going to help my new re-code.
002 // Trey Piepmeier // 04.21.2008 // 1:58 PM
So this is the missing piece to use something like Jellyroll, huh?
Speaking of which, is Jellyroll what you use on this site?
003 // Jeff Croft // 04.21.2008 // 2:18 PM
This would be more of a competitor to Jellyroll than something to use with it. They both offer the ability to import data from external services. Jellyroll does a bi more than that, too, I think.
I don’t use Jellyroll or django-syncr. I wrote all my stuff myself, from scratch. But, the concepts I use are defintiely very similar to django-syncr. The main difference is that I didn’t make models like, “Tweet” and “DeliciousBookmark,” but rather made models like, “Status” and “Photo,” and then wrote importers to import content into those models (there’s a twitter importer for the Status model, and both a ma.gnolia and a delicious importer for the Bookmark model). So, you can use ane importer, multiple importers, or enter content manually into the admin area — or a combination.
004 // Trey Piepmeier // 04.21.2008 // 2:35 PM
Interesting. So does Jellyroll have a way of automatically importing items? For some reason, I thought it was just a structure to hold items that were retrieved with another script.
005 // Jeff Croft // 04.21.2008 // 3:11 PM
I’m pretty positive Jellyroll includes importer scripts for the models it provides…
006 // Trey Piepmeier // 04.22.2008 // 9:29 AM
I see now. So it’s just a matter of writing a cron job to run the script
/bin/update.pyperiodically.