Do you want to use Django-cms on Heroku but don’t know where to start? All you need to do is follow these 13 easy steps, and they will get you on your way.
Create a place to store your project
$ mkdir -p ~/projects
Go into the projects directory
$ cd ~/projects
Clone git repo from github, requires git client.
$ git clone git://github.com/kencochrane/django-cms-heroku.git
Go into the new project directory
$ cd django-cms-heroku
Over the past year I have been testing all of the new python platform as a service companies that have popped up, and I have posted my notes on my blog so that everyone can learn from my experiences. ep.io, apphosted.com, gondor.io, dotcloud.com, DjangoZoom.com, Heroku, Django hosting roundup,
All and all, the platforms were very similar, they allowed you to easily host your python/django project without having to worry about managing a server or other typical system administration duties. Some of the services were more advanced and had more features then others, but since it was still early in the game, that was expected.
New Relic recently added support for python to their awesome web application performance tool, and I have been playing with it on a number of projects.
Installing and configuring new relic is pretty well covered in their own documentation, so there is no reason for me to repeat that here. One thing that isn’t covered in the documentation is how to use new relic if you are using supervisord to control your gunicorn processes, and I’ll take this time right now to show you what I did.
I was looking at the pycon US 2012 website when I stumbled upon the huge list of sponsors, which is really impressive. It got me thinking. Are all of these companies using python? If so, which ones are the best companies to work for?
If it was up to you, and location and money wasn’t a factor, what company would you work for and why? If you already work at one of these companies, can you share what it is you use python for, and what it is like working there?
Heroku the platform as a service (PAAS) company, very popular in the Ruby on Rails community, has now started opening up their platform to languages besides Ruby. They now offer support for Python, Java, Clojure, Node.js, and Scala on their new Cedar stack. Heroku’s Cedar stack is still in beta, but that shouldn’t stop you from trying it out, and that is just what I’m going to do.
6 months ago I wrote a series of blog posts that reviewed all of the cool new django hosting services that were popping up. My goal was to look at them all, and compare them to find out what they had to offer, and to see if I could use them on my future projects. I’m going to review Heroku using the same process that I used to review those other services, so that I can we can compare apples to apples.
When I was at DjangoCon a few weeks ago, it was great hanging out with all of the fellow Djangonauts talking about Django and all of other great technologies. Now that I’m home, I have decided to get off my butt and do something I should have done a while ago.
Without further ado, I am pleased to announce the creation of DjangoMaine.com, a new Django user group based in Portland Maine. We plan on meeting monthly to discuss Django and other python related technologies. We are currently looking for members, and topic ideas for future meetings. If you have any ideas or you are interesting in hearing more, check out our website http:///www.DjangoMaine.com
I recently had my 3 year anniversary at CashStar, and it got me thinking about how fast the last 3 years have gone. When I first started at CashStar there were only a handful of people, and we had nothing, and it was great. We had no products, no customers, which might sound bad at first, but we also didn’t have any customer, or production support issues to slow us down. We could go into work and put in 8 really productive hours, and feel good about yourself when you left that day.
Track a visitors movements across your site.
Possible uses:
Inspired by OpenSymphony’s Java project of the same name. http://code.google.com/p/clickstream/
Add the following properties to your settings file if you want to override the default settings.
When I first started working with django I deployed my apps using apache and mod_python. Then after a little while I started playing with nginx and switched my setup so that nginx was serving the static content and reverse proxied requests back to apache and mod_python. Not too long after that, I switched out mod_python with mod_wsgi and ran mod_wsgi in daemon mode.
This setup worked well for a while, but one thing I never really liked was the fact that I needed to run apache which is pretty heavy even when you strip out all the unused modules. Apache is great, but all I was really using it for was a router between nginx and mod_wsgi, I wasn’t using any of the other features in apache.
For the past 6 weeks I have been trying out all of the new django/python hosting services that are currently available today, and I have been writing about my experiences along the way. It only makes sense to conclude this series of articles with one last article comparing all of the services against each other. It is important to note that many of these services are still in development and aren’t even available to the general public, so I’ll try to keep this article up to date as these services change over time. With that said, don’t take my word for it, go out and try all of these services on your own and find out which one you like the best, you won’t be disappointed.