Actually, I just fixed it - I didn't grant access to port 80 in the
security group. Now it works!
Before, I saw "Page not found".
Thanks!
On Mon, Jan 27, 2014 at 6:48 PM, Avraham Serour wrote:
> what do you see then?
>
>
> On Mon, Jan 27, 2014 at 3:27 PM, Feyzi Bagirov wrote:
>
>> I used these
what do you see then?
On Mon, Jan 27, 2014 at 3:27 PM, Feyzi Bagirov wrote:
> I used these instructions http://nickpolet.com/blog/1/ to install Django
> on AWS EC2 t1.micro instance.
>
> It went well until I restarted apache and was supposed to see the initial
> Django page at the Public DNS a
I used these instructions http://nickpolet.com/blog/1/ to install Django
on AWS EC2 t1.micro instance.
It went well until I restarted apache and was supposed to see the initial
Django page at the Public DNS address: "Now if you view the servers Public
DNS in your browser you should see the d
Karen, Thank you very much. I will try to get another extractor and
see if that fixes the problem. Ed Porter
On Sep 12, 9:37 pm, Karen Tracey wrote:
> I suspect the problem is using WinZip to try to unzip the tarball. Other
> users on this list have reported the same issue in the past. It seems
I suspect the problem is using WinZip to try to unzip the tarball. Other
users on this list have reported the same issue in the past. It seems that
at least some versions of WinZip fail to extract 0-byte files from the
archive file. This is a major problem for any type of Python source project
sinc
I get the below error msg when I try to install Django 1.3.1 on a
windows7 64bit machine.
Django-1.3.1/Django-1.3.1/docs/topics/install.txt says
Installing an official release
~~
1. Download the latest release from our `download page`_.
2. Untar the download
You shouldn't have to. Django should be installed within the virtualenv --
that's kind of the point of virtualenv.
You can have any versions of any Python packages (like Django) without any
effect on your OS's Python installation or other virtualenvs.
--
You received this message because you are
its just dawned on me what i've done.
forgot to add the lines into the top of the django-admin.py to
activate the virtualenv when it is used
tjhanks for the help guys.
On Apr 30, 6:11 pm, Andres Lucena wrote:
> El 30/04/11 18:06, shofty escribi :
>
> > recreated the virtualenv from scratch tota
1.3.0 final
and this time after a clean reinstall, django-admin has indeed created
the settings file i was expecting.
i think im coming round to the idea that i might have django installed
outside of the virtualenvs and somehow the settings.py was created
from that.
On Apr 30, 6:11 pm, Andres Lu
El 30/04/11 18:06, shofty escribió:
> recreated the virtualenv from scratch totally, still got the same
> result. what am i doing wrong here? really cant work it out.
Exactly what is the output?
What is the content of $HOME/.pip/pip.log?
$ cat $HOME/.pip/pip.log
Also, I don't understand what y
recreated the virtualenv from scratch totally, still got the same
result. what am i doing wrong here? really cant work it out.
On Apr 30, 4:11 pm, shofty wrote:
> that folder is empty too.
>
> On Apr 30, 3:40 pm, christian verkerk
> wrote:
>
>
>
>
>
>
>
> > Sometimes virtualenv does not delete a
that folder is empty too.
On Apr 30, 3:40 pm, christian verkerk
wrote:
> Sometimes virtualenv does not delete an existing install out of the
> MY_ENV/build directory causing an upgrade to fail. delete that build
> directory and try again.
>
> Also using sudo can somethings screw things up...
>
>
nah, theres something else going on here, i've successfully
uninstalled then downloaded 1.3 with pip but when i open up the
settings file, the staticfiles stuff and the logging stuff are
missing.
used pip install django==1.3 -E envname
but on the mac its definitely brought down the right version.
Sometimes virtualenv does not delete an existing install out of the
MY_ENV/build directory causing an upgrade to fail. delete that build
directory and try again.
Also using sudo can somethings screw things up...
On Apr 30, 4:34 pm, shofty wrote:
> is there something wrong with the packages at wh
just managed to install 1.3 on my mac, so i guess the problem is on
the debian vps.
is there some sort of package manager i need to point somewhere else?
i'll go do a google.
On Apr 30, 3:34 pm, shofty wrote:
> is there something wrong with the packages at whatever server they are
> hosted?
>
> p
is there something wrong with the packages at whatever server they are
hosted?
pip install upgrade django==1.3 -E envname just isnt working.
installed django into the virtualenv just this morning and its put
1.2.3 in there. can get it to upgrade to 1.3 at all.
if i recall theres a possibility th
My bad. Turns out it was a problem with multiple versions of python
installed. Fixed it.
On May 23, 7:43 pm, Tor Nordam wrote:
> Hello,
>
> I run into a problem when installing django 1.2 on my Mac. I follow
> the recipe on the web page, i.e. I download django-1.2.tar.gz, unpack
> it, and install
Hello,
I run into a problem when installing django 1.2 on my Mac. I follow
the recipe on the web page, i.e. I download django-1.2.tar.gz, unpack
it, and install by running sudo python setup.py install.
After installing, django seems to work fine, but if I delete the
directory I installed it from,
The problem was created by some tar.gz plugin for Total Commander, and
__init__ file had 19MB.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@go
You were right Karen, Total Commander created this problem. __init__
file had 9MB. Unpacked with WinRAR and everything works. Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to th
2009/8/19 Nikola Smiljanić
>
> Django-1.1.tar.gz
> MD5: b2d75b4457a39c405fa2b36bf826bf6b
>
> Same thing. File __init__ in django/utils starts exactly like
> traceback says:
>
> Django-1.1/Django was originally created in late 2003 at World Online,
> the Web division
> of the Lawrence Journal-Worl
Django-1.1.tar.gz
MD5: b2d75b4457a39c405fa2b36bf826bf6b
Same thing. File __init__ in django/utils starts exactly like
traceback says:
Django-1.1/Django was originally created in late 2003 at World Online,
the Web division
of the Lawrence Journal-World newspaper in Lawrence, Kansas.
--~--~---
2009/8/18 Nikola Smiljanić :
>
> I installed Django 1.1 on my Windows 7 machine with 64bit Python 2.6.2
> without any problems, but now I tried to install it on Windows XP with
> Python 2.6.2 and here is what I get:
>
> D:\Django-1.1>python setup.py install
> Traceback (most recent call last):
>
I installed Django 1.1 on my Windows 7 machine with 64bit Python 2.6.2
without any problems, but now I tried to install it on Windows XP with
Python 2.6.2 and here is what I get:
D:\Django-1.1>python setup.py install
Traceback (most recent call last):
File "setup.py", line 69, in
version =
Hi Scott,
> I'm having an issue confirming that Django is installed properly. I
> did what the Django site said: "You can tell Django is installed by
> running the Python interactive interpreter and typing import django."
> So i typed in import django and got:
>
import django
> Traceback (mo
I'm having an issue confirming that Django is installed properly. I
did what the Django site said: "You can tell Django is installed by
running the Python interactive interpreter and typing import django."
So i typed in import django and got:
>>> import django
Traceback (most recent call last):
On Thu, Sep 4, 2008 at 1:45 PM, Denis BUCHER <[EMAIL PROTECTED]>wrote:
>
> Hello !
>
> I have a problem installing django. I followed the instructions but then :
>
Which instructions, exactly? There are various options (installing under
python's site-packages, creati
have a problem installing django. I followed the instructions but then :
>
> # ./django-admin.py
> Traceback (most recent call last):
> File "./django-admin.py", line 2, in ?
> from django.core import management
> ImportError: No module named django.cor
Hello !
I have a problem installing django. I followed the instructions but then :
# ./django-admin.py
Traceback (most recent call last):
File "./django-admin.py", line 2, in ?
from django.core import management
ImportError: No module named django.core
I am running
ssage
From: Dean <[EMAIL PROTECTED]>
To: Django users
Sent: Wednesday, September 12, 2007 12:12:36 AM
Subject: Problem installing django on windows
Hi
I'm having trouble getting jdango working on windows XP.
I've been following the tutorial on:http://thinkhole.org/wp/django-on-
wind
Ahik wrote:
> Hi,
> It seems that 'python' is not in your path.
>
> Try to locate the the path for python.exe. It might be something like:
> C:\Python25\python.exe
> In this case you can type the following:
> C:\django\testproject>C:\Python25\python.exe manage.py runserver
> It should work.
>
> La
Hi,
It seems that 'python' is not in your path.
Try to locate the the path for python.exe. It might be something like:
C:\Python25\python.exe
In this case you can type the following:
C:\django\testproject>C:\Python25\python.exe manage.py runserver
It should work.
Later, you can add the python pa
Hi
I'm having trouble getting jdango working on windows XP.
I've been following the tutorial on:http://thinkhole.org/wp/django-on-
windows/
I have installed all the latest versions of progams that are mentioned
in the tutorial.
but have trouble getting the demo page to work.
I get to this part:
I think I may have fixed it. I did the following:
1) I had moved sqlite, but didn't change the link, so I fixed that.
2) In the settings.py, I entered a path to the database, but not the
actual database name, so I fixed that as well.
3) Then I re-ran the django-admin.py syncdb script
$ django
On Jul 17, 3:50 pm, Collin Grady <[EMAIL PROTECTED]> wrote:
> Check your DATABASE_HOST setting in settings.py - if you have it set
> to a path you can't write to, that would explain the error.
>
> Also, you should be using "manage.py syncdb" not "django-admin.py
> syncdb"
Thanks. Although, I got
Check your DATABASE_HOST setting in settings.py - if you have it set
to a path you can't write to, that would explain the error.
Also, you should be using "manage.py syncdb" not "django-admin.py
syncdb"
--~--~-~--~~~---~--~~
You received this message because you
I am trying to follow Jeff Croft's tutorial:
http://www2.jeffcroft.com/blog/2006/may/11/django-dreamhost/
One difference, I'm trying to install with sqlite3, instead of mysql.
I was doing okay, I think, until this step:
3. Syncronize your Django database with the changes you've made in
the se
37 matches
Mail list logo
