Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

Also, my apologies to OP for misunderstanding his original request :) Cal On Thu, Sep 8, 2011 at 1:26 PM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: > Again - that subject has already been heavily discussed and is already a > work in progress :X > >

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

Again - that subject has already been heavily discussed and is already a work in progress :X Automating the install for the end user is not a simple task - unless you want to go down the VM Appliance route. See the following threads:

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

Cal, He's not looking to automate the install for the Developer of a Django Project, but for the End Users of a Django Project. So if I, or another developer wrote a WordPress clone using Django and then allow a third party to come and download my Wordpress clone and easily install it. On

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

The subject of self contained deployments has already been *heavily* discussed in other threads. Self contained / single binary deployments is something that Roberto @ UNBIT is currently working on (and myself), and if you do a search on the mailing list, you'll see tons of ideas on this already.

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

This is a hard question. It would probably be nice to offer a self contained deployment that nginx/apache could just proxy too, maybe pick that as the default, and then add in writing a fcgi or wsgi file for use with regular hosting. On Thursday, September 8, 2011 at 7:34 AM, graeme wrote: >

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

He wants to be able to emulate the installation of a typical PHP CMS. This is often 1) get database username and poassword, 2) copyfiles to server, 3) navigate to an install URL, 4) fill in db username and password and other config on a set of forms on web page. Installing Django and the app you

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

On Sep 8, 12:45 am, Calvin Spealman wrote: > Can you explain to those of us to whom it is not obvious, what is the > point of this proposal? I don't understand what problem it would > solve. > > > > > > On Wed, Sep 7, 2011 at 10:41 AM, Alec Taylor

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

On Sep 8, 12:45 am, Calvin Spealman wrote: > Can you explain to those of us to whom it is not obvious, what is the > point of this proposal? I don't understand what problem it would > solve. The commonest use case would be something like this: Someone wants to use a Django

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

Looks like the initial mockup for the final display didn't Ctrl+V properly, here it is: http://i55.tinypic.com/s5fivd.png The problem I'm trying to solve is one of deployment (and minimalist

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

Can you explain to those of us to whom it is not obvious, what is the point of this proposal? I don't understand what problem it would solve. On Wed, Sep 7, 2011 at 10:41 AM, Alec Taylor wrote: > Good morning, > > I have just recently starting migrating over from

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

I would agree with Donald, and expand on that to say that an installer would probably be best written in php for widest compatibility. A php based installer would run outof the box on most webservers, and be able to give a guided overview of the python/web environment setup. It would easily be

Re: Streamlining DJango Deployment — Novel idea from the world of CMSs

We talked a little on IRC, but just thought i'd reiterate my thoughts. This should not be in core, and I don't believe it ever has a chance of being in core. That being said, I think that an external "installer" app like this wouldn't be the worst thing in the world, and could help to make

Streamlining DJango Deployment — Novel idea from the world of CMSs

Good morning, I have just recently starting migrating over from WordPress and Drupal to the world of DJango. First of all, let me say that yes, I am aware that DJango is not a CMS!!! Now, onto my suggestions on how to streamline DJango deployment. = What's wrong with the current method?