Re: Using the Eclipse mysite>django>custom command(manage.py$(custom_command)) function

You can't createuser, becouse this command need user input. For this case better run manage.py directly from console. Sorry, can't help you with this. On Sun, Jun 26, 2016 at 12:51 AM, Gary Roach wrote: > i did as you suggested and tried it with runserver. It worked. I tried the > same thing with

Re: Using the Eclipse mysite>django>custom command(manage.py$(custom_command)) function

Hello, that message tells you everything. As there is no tty (ie. a terminal that can read user input and write some output), createsuperuser won’t run. I don’t know eclipse, but if you can force it to run commands within a tty, you won. Otherwise you will have to use the command line. Well, exc

Re: install with package manager or pip

The virtualenv folder should not be your root folder. It's a separate folder. You can keep them all in a single location or put each of them in a subdir of your projet. You start using a virtualenv with "source venv/bin/activate". After this, the current terminal will use the virtualenv in the fol

Re: install with package manager or pip

On Sunday, June 26, 2016 at 11:13:20 AM UTC-5, ludovic coues wrote: > > The virtualenv folder should not be your root folder. > it's not. VirtEnv is base. VirtEnv/mysite is the virtualenv. this is where manage.py is located then VirtEnv/mysite/mysite and .../mysite/polls this is what the tut

Re: Questions about Deploying django for production using apache and mod_wsgi.

On May 26, 2016, at 12:12 PM, Bruce Whealton wrote: > > Hello all, > I have a few questions of which I am not finding answers. > 1) If I export my development db (Postgresql) and then import it into > production database, > won't I be pulling in a very weak password that I used for deve

Re: install with package manager or pip

I setup my folder this way: /project/VirtEnv /project/mysite File like requirement.txt, readme, licence and .gitignore are in /project, /project/mysite contain manage.py and all the django file, /project/VirtEnv is managed by virtualenv and pip. I don't look at the content of the folder most of the

inconsistent namespacing for fixture files vs. template files (and everything else)?

In the Django code wiki topic on Fixtures , there is a recommendation to "namespace" fixture files for an app by using the app name as a prefix in the filename (the example given is *myapp/fixtures/myapp_testdata.json*). But the Django tutorial on