[autalpha]

I actually have this debate with myself every time I think that I am close to the point of deploying my work (heh, that's another story). But every time I do the calculation, I just don't get how AWS would be more beneficial to me vs sticking with Linode. AWS' pricing would be much more than Linode's model. So for a while, I think I am set on this resolve:

Using Linode for my app and host static files on S3 and maybe another cloud provider like Rackspace for failover in case the clouds go down.

I am hoping that I would have a luxury problem once my app is doing well. When I have that kind of traction, it's a different story. But until then, it's more logical to stick with a VPS.

By the way, are you making updates to your production site frequently? Your carousel isn't working correctly yet.

I know you use django (from another post I think). Have you thought about using social network login? I used django-allauth and it has been working very well for me. Good luck!

[philgo20]

We push to production 3-4 times a day. You mean the carrousel on the home page ? I'll take a look. That page hasn't really been touched since we started developing and needs a complete makeover. Thanks for the heads up !

We currently our own LinkedIn login to create account as we use their API to match candidates and jobs. Next step is to add Facebook and Twitter as alternative login.

We were thinking to go with django social-auth to cover al bases. http://uswaretech.com/blog/2009/08/django-socialauth-login-v...

Had you compared it to allauth ? I'll take a look, hadn't seen that one.

thxs !