Lots of errors after deploying and going live

[Dave Ko]

Hi guys, so this is a very general post, I have been working on a django blog following Corey Schafer's Django tutorial.

Everything went smoothly on local machine, but once I deployed it, I am having all kinds of troubles.

From password_reset (still not solved) to uploading image ran into error of register_open() missing factory, all of the troubles didn't occur on local machine.

I had some experience with expressjs development, there were no difference before and after deploy.

As for Django, there are so many errors I couldn't find the answer including here and stackoverflow, have you guys face similar situation?

here is my git repository, please have a look and point out the problems i have https://github.com/koloyyee/roasitas

[Mike Dewhirst]

Dave

You are absolutely right. Django does go smoothly on the local machine.
However, if you relocate that exact smoothness to a different
environment there will definitely be some jagged edges to contend with.

I'm sure you remember tweaking things to achieve local smoothity. You
will have to do precisely the same sorts of things for your production
environment.

The trick is to abstract everything which interfaces with the
environment and (in my case) write little functions to fetch the
required bits and pieces or adjust bits and pieces of the
staging/production environment to suit.

The most likely cause of your problems will be different locations for
static files between here and there. Another cause might be different
credentials for accessing the database here versus there. Maybe you have
done the right thing and kept all secrets out of your repo and thus you
need to find a way to use the correct secret in each location.

Perhaps you are using different versions of Python or Django itself or
one or more of your supporting apps/libraries is different in the other
environment?

There are ways and means of keeping things totally smooth in any
combination of environments but you'll have to be a bit more specific
with your questions and requests.

Cheers

Mike

> --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-users...@googlegroups.com
> <mailto:django-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/b0066211-a642-4e64-9728-55a824930b78%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/b0066211-a642-4e64-9728-55a824930b78%40googlegroups.com?utm_medium=email&utm_source=footer>.

[maninder singh Kumar]

Great answer Mike !

Maninder Kumar about.me/maninder.s.kumar

To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b9085dcc-296d-79c1-41ef-098d5ad8fa60%40dewhirst.com.au.

[onlinejudge95]

It might be out of point but the moment you start noticing these errors repeatedly is the time you start considering using docker.

--

You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b0066211-a642-4e64-9728-55a824930b78%40googlegroups.com.

[Juan Pablo Romero Bernal]

Hi Dave,

First of all, what kind of environment are you using to production deployment ?  May be if you

give us some details about it we can help you.

Bye,

--

You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b0066211-a642-4e64-9728-55a824930b78%40googlegroups.com.

--

Juan