Right now, I am having problem with the installation of linux ( I will try
to figure that out if not, will contact you about that). I do have a problem
with installing the Django on Linux. I am new to the Django world, so I've
already downloaded the Django to my usb drive. Is there a certain way I
But in order to do that, don't I need to have the Django source file
somewhere in my computer/ or in my case.. I've downloaded the Django tar
file to my usb flash drive? The command you gave me, that works in the linux
world, right? Like I said, I am new to this Djando materials.
On Thu, Jan 20,
I cannot install the Ubuntu, I have to use Derbian for work purposes.
On Thu, Jan 20, 2011 at 3:45 PM, Shawn Milochik wrote:
> On 01/20/2011 04:40 PM, Kimberly Harvey wrote:
>
>> Right now, I am having problem with the installation of linux ( I will try
>> to figure tha
MY boss never mentioned about using the Ubuntu, just want me to use the
Debian.
Thanks
On Thu, Jan 20, 2011 at 3:58 PM, Ivo Brodien wrote:
>
>
> > But in order to do that, don't I need to have the Django source file
> somewhere in my computer/ or in my case.
>
> apt-get gets packages from the
Thanks for the tips and advices. I still believe Django can be run on the
linux-Debian version. There are some updated Django which I've already saved
on my usb flash drive which I will soon run some commands on the linux as
some other people has advised me to do so. The person wants me to learn mo
That is exactly what I am doing right now, I between the crawl and walk
phrase now, lol.
On Thu, Jan 20, 2011 at 9:23 PM, Mike Ramirez wrote:
> On Thursday, January 20, 2011 07:09:10 pm Kimberly Harvey wrote:
>
> > Thanks for the tips and advices. I still believe Django can b
it still doesn't work. I typed it like you've suggested and it keeps saying
that the database ENGINE has not been set.
On Sun, Jan 23, 2011 at 5:11 AM, Mark Penix wrote:
> your whole engine line should read
> 'ENGINE': 'django.db.backends.sqlite3'
>
> --
> You received this message because you a
3, 2011 at 6:47 PM, Kimberly Harvey wrote:
>
>> it still doesn't work. I typed it like you've suggested and it keeps
>> saying that the database ENGINE has not been set.
>>
>>
> If you are using ENGINE by itself, you need to be using Django 1.2 or
> higher and
Problems ( this is very frustrating!).
In the settings.py file, I'm using the django 1.2 or higher, so it has
ENGINE : '", and whatsnot
I set the ENGINE to sqlite3, that didn't work. Then I added the path, and
that still doesn't work. It keeps saying that the ENGINE has not been set. I
have no clu
# Set to empty string for
> localhost. Not used with sqlite3.
> 'PORT': '', # Set to empty string for default.
> Not used with sqlite3.
> }
> }
>
> This will allow everyone to see if you have mucked up some othe
inking, so I apologize once again. I am using Django
1.2 and to ensure that the Django has been installed, I run a test in the
shell and it exists.
On Sun, Jan 23, 2011 at 7:38 PM, Karen Tracey wrote:
> On Sun, Jan 23, 2011 at 8:27 PM, Kimberly Harvey wrote:
>
>> Problems ( th
By the way, it is Django 1.2.4 to be exact
On Sun, Jan 23, 2011 at 7:38 PM, Karen Tracey wrote:
> On Sun, Jan 23, 2011 at 8:27 PM, Kimberly Harvey wrote:
>
>> Problems ( this is very frustrating!).
>>
>> In the settings.py file, I'm using the django 1.2 or higher,
used with sqlite3.
>>> 'HOST': '', # Set to empty string for
>>> localhost. Not used with sqlite3.
>>> 'PORT': '', # Set to empty string for
>>> default. Not used
'ENGINE': 'django.db.backends.sqlite3', # Add
>>>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>>>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', &
>>>>>> wrote:
>>>>>>
>>>>>>> Rather than have us guess what is in your settings file, post that
>>>>>>> whole section. For example:
>>>>>>>
>>>>>>> DATABASES = {
>>>>>
> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton
>>>>>> wrote:
>>>>>>
>>>>>>> Rather than have us guess what is in your settings file, post that
>>>>>>> whole section. For example:
>>>>>>>
>>>>>
It is not working at all, still facing the same configuration problem
(ENGINE IS NOT SET).
On Sun, Jan 23, 2011 at 9:19 PM, Steven Elliott wrote:
> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
>'default': {
>'ENGINE': 'django.db.backends.sqli
I am using pico editior and I've been saving the work by using the control
X.
On Sun, Jan 23, 2011 at 9:25 PM, Steven Elliott wrote:
> Also, what editor are you using? if its not an IDE-type thing remember to
> save your work in the editor. If you are coming from the Windows programming
> world
it says that the _file_ is not defined.
On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>>
>> Copy and Paste the following to replace your entire DATABASES tuple:
>>
>> DATABASES =
I've provided the full errors in the post, it is there. ( same errors as
I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as
I'm encountering the same after I've copied and paste the print inside the
settings.py file at the end)
On Sun, Jan 23, 2011 at 9:40 PM, Graham Dump
Thank you for the advices. I've done some Python codes in the past and
recently. I already have a Python code that I will need to use to create a
Django website ( response to Steven).
(Response to Graham):
Traceback ( most recent call last):
File "manage.py", line 11, in
execute_mana
Traceback ( most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File "/usr/lib/python2.5/site-
packages/django/core/management/_init_.py", line 438, in execute manager
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
37
The output was produced with the print __file__ and print 'DATABASES',
DATABASES at the end of the settings.py file.
On Sun, Jan 23, 2011 at 10:18 PM, Kimberly Harvey wrote:
> Traceback ( most recent call last):
> File "manage.py", line 11, in
> execute
Please do the following and provide the output:
pwd
MY OUTPUT: /home/username/wikicamp
Now run 'python' from the command line and do the following, providing the
output to us:
import settings
print settings.__file__
import wikicamp.settings
print wikicamp.settings.__file__
after imp
I did not modified the manage.py file
On Sun, Jan 23, 2011 at 10:44 PM, Kimberly Harvey wrote:
> Please do the following and provide the output:
>
> pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the followin
Sorry about that, there is nothing showing for either echo $PYTHONPATH and
echo $DJANGO_SETTINGS_MODULE
I am currently reading your messages.
On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wro
/home/username/wikicamp/wikicamp/settings.py --> THIS DOES NOT EXIST
WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
settings.py is there.
On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
> Sorry about that, there is nothing showing for either echo $PYTH
our home directory, then you have a settings.py sitting in
> your home directory which is the problem. Rename any settings.py file you
> home directory to something else.
>
> mv ~/settings.py ~/settings.py.broken
>
> In short, you have more than one settings.py file somewhere where i
an 23, 2011 at 11:25 PM, Kimberly Harvey wrote:
> The directory I did it from was from my home directory. I've moved the
> files like you've indicated by using mv settings.py settings.py.broken.
>
> Should I go ahead and type in the command as python manage.py syncdb to see
>
m.
>>>
>>> If you didn't run this from inside of site directory as was expecting and
>>> you did it from your home directory, then you have a settings.py sitting in
>>> your home directory which is the problem. Rename any settings.py file you
>>>
gt; print settings.__file__
>>>>>
>>>>> import wikicamp.settings
>>>>> print wikicamp.settings.__file__
>>>>>
>>>>> after importing setting
>>>>> print settings.__file__
>>>>> OUTPUT: sett
>>>>
>>>>>>>> /home/username/wikicamp/wikicamp/settings.py --> THIS DOES NOT
>>>>>>>> EXIST
>>>>>>>>
>>>>>>>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
>>>&g
response to messages:
I am using the Django inside the Linux-Debian on my windows 7 machine. This
is what happen when I opened the terminal in the Django..
command: python manage.py runserver
It runs fine... 0 errors.
It shows me the url which is http://.. then I went to the browser on
the Dj
Karen,
It worked after I used the mv command to move the settings.py
settings.py.break and then did another move where from settings.py.break to
settings.py, then I ran the server by using the manage.py syncdb. I do not
understand why that even worked ( I didn't want to use the settings.py.b
yes the sqlite package is installed. I installed the Django and the python,
and I test it to ensure it is there and it is.
On Mon, Jan 24, 2011 at 12:48 PM, Kimberly Harvey wrote:
> Karen,
>
> It worked after I used the mv command to move the settings.py
> settings.py.break
I ran the browser in the linux.
On Mon, Jan 24, 2011 at 12:57 PM, Javier Guerra Giraldez wrote:
> On Mon, Jan 24, 2011 at 1:43 PM, Kimberly Harvey
> wrote:
> > I am using the Django inside the Linux-Debian on my windows 7 machine.
>
> do you run your browser in Windows or Lin
1 at 1:15 PM, Steven Elliott Jr wrote:
> Have you tried running it on a different port? Can you post the actual
> error message you get?
>
> -Steven Elliott Jr
>
> On Jan 24, 2011, at 2:05 PM, Kimberly Harvey wrote:
>
> I ran the browser in the linux.
>
> On Mon
Thanks, I restarted the whole Django program. Will send feedbacks if any
problems this week.
On Tue, Jan 25, 2011 at 12:17 AM, raj wrote:
> If none of above seems to work, You may be using a browser like google
> chrome, which by default ignores the localhost.
>
> --
> You received this message
38 matches
Mail list logo
