Several times now, I have struggled to find a suitable Django-friendly host for my projects. Each time, the community has responded with advice on where these projects should or shouldn’t call home.
Now there’s a place this helpful information can call home.
In your quest for a django-friendly web host, you need not look any further than djangofriendly.com.
Beginning with the basic host data collected on the Django-friendly wiki page, djangofriendly.com adds the following:
Voting: Like your host? Vote ‘em up. Don’t like your host? Vote ‘em down. Hosts with the best score get promoted to the top of the list.
Commenting: Let the community know why you love/hate your current or past hosts.
Links: Find or add tutorials and other helpful information for each listed host.
Together, this information should provide users with plenty of support in finding the best Django hosting environments.
The site has been a lot of fun to plan and build. I hope the Django community that has given so much to me finds this useful. It’s my way of giving a little something back.
I plan to add the ability for users to add new, and edit existing hosts shortly. I’m also open for any other suggestions (leave them in the comments)!
Also, some hosts that provide referral programs are linked with embedded referral codes. Djangofriendly does not exist to make money, but I figure if the referral codes don’t harm the experience, there shouldn’t be any conflict. I hope the users feel the same way, but if there’s enough negative feedback, I’ll consider changing the current affiliate policy.
Djangofriendly was built on top of Django, of course, but also django-voting, django-registration, and django-tagging. I give many thanks to the authors of these great applications.
Please, enjoy the new site, and let the community know which hosts are the friendliest. The more voting and commenting, the better this resource will be!
Looks good, I've reviewed my host.
BTW, you need to set DEBUG = False. I got your debug page when the memcache backed timed out.
When I set DEBUG = False this morning, my redirect from / to /hosts/ threw a 404. Any ideas why this might happen?
Okay, apparently when there aren't proper 404/500 templates, redirects crash and burn. Fixed.
Congratulations by the site, but when I try to create an account or to reset my password I get the error:
The dreaded 500 error
Errors aren't very friendly. So sorry you had to see one.
You want me to register to vote on my hosting provider?
How many usernames and passwords should I leave strewn about the web?
I suspect most people will use the same username and same password for this as other django sites, how do we know you're not hijacking them?
I'll come back when I can use OpenID thanks.
Alberto -
I just went through the process and was able to register without a problem. I did however find a bug in the password change functionality that I have fixed. It appears your account hasn't been activated yet - did you get an activation email at any point?
Noah -
The password protection is to prevent hosting providers from anonymously upping their vote counts, and provide accountability for all the comments posted.
I originally planned to work with Ross Poulton, the friendly guy behind djangosites.org, and integrating with his user database to reduce repetitive signups, but the logistics behind sharing servers (and too many timezones between us for quick communication) prevented djangofriendly from launching in partnership with djangosites.
As for hijacking the info? You're welcome to see the code I'm using for handling registration. django-registration
I don't currently know enough about OpenID to implement it. There are other priorities ahead of this. If you'd like to contribute code to integrate this setup with OpenID, I'd be very receptive.
+1 on Noah
I will also come back when OpenID-Identifikation is available! I don't like to register on tausend of websites, but I would use my OpenID-Account to use your site, because the idea is great. The layout is also very fine.. I like it!
~ Bernd
Another +1 for OpenID. Would love to vote up SliceHost, my excellent host, but I'm not compelled to sign-up for another site. Especially not something single-use such as this.
There is lots of info on the interwebs for using OpenID with Django. Simon Willison is a huge fan of OpenID, he's written up a bit on his site. Here's his google code project, http://code.google.com/p/django-openid/
I can understand where Ryan's coming from on the OpenID info. Sure you can throw a project at him, but there's not enough documentation out there (especially for those of us who aren't Python-native) to easily integrate it.
In addition to hooking up logging in via OpenID, I'd also have to figure out how to make existing libraries (namely django-voting and django.contrib.comments) play nicely with OpenID as well. As it stands now, each requires the Django User model for their ForeignKeys. This isn't as simple as being too lazy to read some docs, and it goes deeper than my own application.
Simon has brought it to my attention elsewhere that OpenID can integrate with the Django user model. I'll be looking further into all this as soon as I can.
"Simon has brought it to my attention elsewhere that OpenID can integrate with the Django user model. I'll be looking further into all this as soon as I can. "
Please post your findings. Love the site!
Comments are disabled for this item
© 2007-2008 Ryan Berg // Built with Django // Hosted on WebFaction
Discussion