Re: 404 handler not working on live hosting environment

Thanks Kenneth, we were also discussing yesterday how we need to have a "safer" deployment strategy.

We are using TortoiseSVN for version Control.

On Fri, Sep 10, 2010 at 4:31 AM, Kenneth Gonsalves <lawgon@au-kbc.org> wrote:

On Thu, 2010-09-09 at 14:31 +0200, Sithembewena Lloyd Dube wrote:
> Yes, both the Django and Python versions on dev and prod match. We are
> running Django 1.2.1. and Python 2.6.5.
>
> On our dev server, we use Django's server instead of Apache.
>
>

actually to avoid problems like this in production you should use a
3-stage deployment:

1. develop with runserver
2. have a staging server (maybe on the same devel machine) which tries
to replicate the production environment
3. then move the code/changes to the production server.

(I hope you are using some VCS?)
--

regards
Kenneth Gonsalves

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
Regards,
Sithembewena Lloyd Dube
http://www.lloyddube.com

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.