For me, the main reason to use virtualenv has nothing to do with
security or anything like that, is the convenience of having different
projects with different sets of requirements not interfering with each
other

2012/3/7 backdoc <backdoc...@gmail.com>:
> I've never set up virtualenv, so I can't speak to that.  But, how is
> installing Django the same way that I install any other application
> more of a risk?  If an installer tries to write to /usr/local/bin/,
> then it needs elevated permissions to do so.  I would assume from that
> point on, the remainder of the time, the program runs within the
> context of the user who executed it, just like any other shell
> commands like tar, ls, mv, rm, python, and so on.
>
> While the web server is running, wouldn't it execute any Django
> commands within the context of the web user, like www-data?  When I
> installed WSGI, I used Synaptic.  To use Synaptic, if you start it as
> a regular user, you have to give root password.  How would is that
> different?
>
> You may have very good answers.  I'm not saying I'm right and you're
> wrong.  But, I don't see the problem.
>
> On Mar 7, 4:21 pm, Andre Terra <andrete...@gmail.com> wrote:
>> Again, don't install as root, use virtualenv. This will save you headaches
>> in the future, and unless you have an inexcusable reason to have Django run
>> as root, you shouldn't.
>>
>> Sincerely,
>> AT
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Mar 7, 2012 at 6:28 PM, backdoc <backdoc...@gmail.com> wrote:
>> > I think you might need to install as root or sudo.
>>
>> > From memory.....
>>
>> > sudo python setup.py install
>>
>> > Also, try executing "which django-admin.py" at the terminal.  That
>> > will tell you the location of the executable.  Basically, I'm curious
>> > if it will even find it, as I'm thinking it didn't install at all.  I
>> > just installed the 1.4 rc last night on Debian.  I didn't have any
>> > issues.
>>
>> > On Mar 7, 8:36 am, Clark <ccr...@gmail.com> wrote:
>> > > After installing Django I am attempting to start a new project.  After
>> > > creating a directory for this, I tried using the command: "django-
>> > > admin.py startproject mysite".
>>
>> > > but I'm getting the message "-bash: django-admin.py: command not found
>> > > ".
>>
>> > > So, I've tried running this:
>>
>> > > "sudo ln -s library/python/2.6/site-packages/django/bin/django-
>> > > admin.py /usr/local/bin/django-admin.py" in which i get "file exists"
>> > > and I still get the same problem when running the startproject.
>>
>> > > Only other piece of info is that during installation I had a "error: /
>> > > usr/local/bin/django-admin.py: No such file or directory".  But I can
>> > > cd into that directory and see the django-admin.py file.
>>
>> > > Thanks!
>>
>> > --
>> > 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@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > django-users+unsubscr...@googlegroups.com.
>> > For more options, visit this group at
>> >http://groups.google.com/group/django-users?hl=en.
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>



-- 
Andrés Reyes Monge
armo...@gmail.com
+(505)-8873-7217

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to