Seriously, though, this is cool, and every developer-entrepreneur should do something like this just to get the experience of actually shipping a web app.
I'll come back to the site eventually and finally get around to learning how to write those unit tests. :)
Rushing through learning RoR and not a) learning Ruby and b) actually taking your time to write some tests goes against what is arguably the best practice for learning RoR properly.
Throwing together one app is a start down a path to learning RoR, it's not actually "learning Ruby on Rails". They are two different things.
Where you're so captivated in all the shiny Ruby Gems that you don't take the time to learn what they actually do.
Hopefully you are going to take a long journey with Rails!
I'm impressed. Would like some words of advice from you, as I am attempting something similar but less ambitious. Ok to contact you via email?
Oh, and seven days? Really? Even with such a thorough explanation I have to wonder how much time people have on their hands to buckle down and do this. This can't be something that's done sporadically. Not in 7 days.
Is there something like that SaaSTemplate for Django?
For example, for Twitter - you'll encounter that there isn't necessarily a one-size-fits-all Twitter plugin that's specific to Django. Instead, you might need an authentication plugin which will store relevant Twitter information (id, token) and then use a Python Twitter plugin to do the kind of neat stuff the author has accomplished.
I prefer Django because it's more explicit and there is less magic. This is also good for beginners because it's easier for you to track down where things might be going wrong for you. Django might not have the best community-support (no railscast equivalent).
I don't know.
Bonus commentary: Rails is not for the faint of heart. It will suck, but just dive in and see if you can hack it. Then stay humble and keep on pushing yourself.