hing more without looking at the
actual code/setup. But since runserver works, perhaps your production
environment is pointing to an older version of Django?
Regards,
Abhaya
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe
This looks fine. Are there any errors in the web server logs?
Regards,
Abhaya
On Mon, Apr 27, 2015 at 10:23 PM, dk wrote:
> we decided to test django 1.8, using python manage.py runserver works
> great. but now the production wsgi stop working,
> I remember there was a change betwee
ration representing all the db changes since the
last deploy. Hope this helps.
Regards,
Abhaya
On Sat, Apr 25, 2015 at 5:56 PM, Timothy W. Cook wrote:
> Django 1.8 Python 3.4 PostgreSQL 9.3
>
> During development I am creating several migrations. It seems unnecessary
> to keep these since the
oing with option 2 for my case.
Regards,
Abhaya
--
-
blog: http://abhaga.blogspot.com
Twitter: http://twitter.com/abhaga
-
--
You received this message because you are subscribed to the Google Groups
&qu
Hi,
I am trying to get stated with new relic on my django app. I am new to
new relic. Can you please guide me on steps to get started in
developer mode and how to use it in live server.
I did try to find tutorials on this, but it looks like I could not
find a good one.
--
You received this messag
Hi Gaston,
I am also pretty new to python. Once I had a similar issue, it turned
out to be permissions on the directories. Since you are creating a
symlink, make sure that all the directories have appropriate
permissions.
Regards,
Abhaya
On Dec 17, 2:22 am, Gaston wrote:
> I believe I'
6 matches
Mail list logo