4 ms·

What's the fastest anyone has deployed a Python / Django app?

7 points by ogreman 12y ago

gjvc 12y ago
not sure what you mean, but I have found nginx, uwsgi, pypy, psycopg2cffi a fast combination :-)
- ogreman 12y ago
  Thanks! To be more clear, I meant approx. times (if possible) and which stack (as you've done) or PaaS was used.
mrkmcknz 12y ago
Heroku might be worth looking at if you're just getting started with some basic Python deployment. Although it wont really teach you anything about deployment other than some Git basics. Suggest starting here: http://www.deploydjango.com/ http://www.deploydjango.com/
27182818284 12y ago
I had a HUGE learning curve with Heroku. I'd recommend against it. I think in the end, it would have been cheaper and faster to deploy to just a generic cloud server on Digital Ocean or Rackspace or whatever.
- ogreman 12y ago
  From experience with most providers, Heroku has been the fastest and easiest to deploy to. It's interesting to hear an alternative experience. What would you say got in the way for you?
  - 27182818284 12y ago
    Just a ton of little things that piled up. No single problem took a significant amount of time, but it seemed like every little task took 5 minutes here, 5 minutes there. For example, and this was last summer so my memory is a bit vague, but one of the commands issued without an argument wouldn't give the "wrong argument" message you expect, but instead would just error out. So I thought something was really broken, but I was just missing a -- flag on something. Wasted a few hours. That's what I mean by learning curve.
  - collyw 12y ago
    My first attempt at deploying to Heroku was a very simple admin based app to demonstrate something to a friend. That was really simple and went without problems. Then I tried a slightly larger app and it was a disaster. A lot of the problem is that I develop in Aptana / Eclipse, and the file layout that Aptana expects is different from what Heroku expects (Aptanas has one extra directory at the top level, yet Heroku expects some of its files in the top level directory). In the end I have a slightly hacky try / except around some imports in urls.py to get around the problem.

7 points by ogreman 12y ago

gjvc 12y ago

not sure what you mean, but I have found nginx, uwsgi, pypy, psycopg2cffi a fast combination :-)

ogreman 12y ago
Thanks! To be more clear, I meant approx. times (if possible) and which stack (as you've done) or PaaS was used.

mrkmcknz 12y ago

Heroku might be worth looking at if you're just getting started with some basic Python deployment. Although it wont really teach you anything about deployment other than some Git basics. Suggest starting here: http://www.deploydjango.com/ http://www.deploydjango.com/

27182818284 12y ago

I had a HUGE learning curve with Heroku. I'd recommend against it. I think in the end, it would have been cheaper and faster to deploy to just a generic cloud server on Digital Ocean or Rackspace or whatever.

ogreman 12y ago
From experience with most providers, Heroku has been the fastest and easiest to deploy to. It's interesting to hear an alternative experience. What would you say got in the way for you?
- 27182818284 12y ago
  Just a ton of little things that piled up. No single problem took a significant amount of time, but it seemed like every little task took 5 minutes here, 5 minutes there. For example, and this was last summer so my memory is a bit vague, but one of the commands issued without an argument wouldn't give the "wrong argument" message you expect, but instead would just error out. So I thought something was really broken, but I was just missing a -- flag on something. Wasted a few hours. That's what I mean by learning curve.
- collyw 12y ago
  My first attempt at deploying to Heroku was a very simple admin based app to demonstrate something to a friend. That was really simple and went without problems. Then I tried a slightly larger app and it was a disaster. A lot of the problem is that I develop in Aptana / Eclipse, and the file layout that Aptana expects is different from what Heroku expects (Aptanas has one extra directory at the top level, yet Heroku expects some of its files in the top level directory). In the end I have a slightly hacky try / except around some imports in urls.py to get around the problem.