Re: Trouble with Django in production server.

Instead of hard-coding paths, check out os.path, os.abspath and os.sep (and the rest of the os module) for such needs. I usually declare a PROJECT_ROOT var at the top of my settings.py using the aforementioned os module, and then hang paths (like your db path) off of that instead of building each path individually.

Glad you figured it out.

Sent from my iPhone

On Mar 1, 2014, at 5:41 PM, Omar Acevedo <omaace@gmail.com> wrote:

To see if it worked, and yes it did!
So, I'm just having trouble with the paths.
I'm using a virtual environment.
So I guess I'll have to deal with the paths.

Thank you a lot anyways!!! :)

On Sat, Mar 1, 2014 at 8:39 PM, Omar Acevedo <omaace@gmail.com> wrote:

I explicitly wrote '/home/catacafe/.env/env/lib/python2.7/db.sqlite3' in the NAME option of the DATABASES dictionary.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAH_X0gMnjh%2BOy5AQC2rw_LtKEjnWU-YVY_yBH3AzTMoSP%2BCiXw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.