Re: Trouble with Django in production server.

On Tue, Mar 4, 2014 at 7:11 PM, Daniel Roseman wrote: > That's why, as everyone keeps telling you, you need > to activate the virtualenv in your server, which is normally done in the > wsgi file. Is it? I keep my wsgi.py exactly as startproject created it, I set

Re: Trouble with Django in production server.

On Tuesday, 4 March 2014 00:54:48 UTC, Omar Acevedo wrote: > > Also there's a file called .bashrc which activates the virtualenv. > This is the line that does that: > source /home/userName/.env/env/bin/activate > So it runs (the virtualenv) always. > But the web server is not running as you!

Re: Trouble with Django in production server.

Also there's a file called .bashrc which activates the virtualenv. This is the line that does that: source /home/userName/.env/env/bin/activate So it runs (the virtualenv) always. Probably I'm still having problem because of the database file, ... but I don't know that else to do! Where to

Re: Trouble with Django in production server.

No, the server itself it's not running in a virtualenv. Yes, it is a shared hosting service which it's both domain and account. And about the server, ... well, (idk), I'm using FastCGI, also, I followed this tutorial first -> https://help.asmallorange.com/index.php?/Knowledgebase/Article/View/140

Re: Trouble with Django in production server.

On Sunday, March 2, 2014 10:36:51 PM UTC-4:30, Omar Acevedo wrote: > > I have inside a file called .bashrc, > source /home/userName/.env/env/bin/active, > which makes me be in in a virtual environment already, no? > It has a (env) to the left all the time. > I presume that that is "activating

Re: Trouble with Django in production server.

I have inside a file called .bashrc, source /home/userName/.env/env/bin/active, which makes me be in in a virtual environment already, no? It has a (env) to the left all the time. I presume that that is "activating virtualenv to run the server", right? (: On Sun, Mar 2, 2014 at 7:19 PM, Camilo

Re: Trouble with Django in production server.

You also should be activating your virtualenv to run the server. On Saturday, March 1, 2014 8:46:10 PM UTC-4:30, jondbaker wrote: > > 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

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

Re: Trouble with Django in production server.

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 wrote: > I explicitly wrote

Re: Trouble with Django in production server.

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

Re: Trouble with Django in production server.

While trying and trying different stuff, turned out to be a bad path configuration with the NAME inside the DATABASES dictionary within the settings.py file. On Sat, Mar 1, 2014 at 8:34 PM, Jonathan Baker wrote: > Are you using multiple settings files, for

Re: Trouble with Django in production server.

Are you using multiple settings files, for example: dev.py, pro.py, etc.? Are you sure that the settings file you're using is configured to use the database on your production server? On Sat, Mar 1, 2014 at 5:12 PM, Omar Acevedo wrote: > Yes! > > > On Sat, Mar 1, 2014 at 8:11

Re: Trouble with Django in production server.

Yes! On Sat, Mar 1, 2014 at 8:11 PM, Jonathan Baker wrote: > When you ran the 'syncdb' management command, was 'auth_user' listed in > the output as a table that was created? > > > On Sat, Mar 1, 2014 at 3:52 PM, Omar Acevedo wrote: > >> Hello

Re: Trouble with Django in production server.

When you ran the 'syncdb' management command, was 'auth_user' listed in the output as a table that was created? On Sat, Mar 1, 2014 at 3:52 PM, Omar Acevedo wrote: > Hello people, I'm having an issue in/with Django, which is on a shared > hosting, and I'm using virtualenv and

Trouble with Django in production server.

Hello people, I'm having an issue in/with Django, which is on a shared hosting, and I'm using virtualenv and fastcgi. (<- saying this, just in case it helps in something) I'm getting "OperationalError at /admin/ no such table: auth_user" after entering my credentials (username & pw) set when