Retroactively seting up virtualenv

[Rich Shepard]

My business is not web site development and I'm starting development of a
django project for my own use. Django-1.11.3 is installed in
/usr/lib/python3.6/site-packages/django and my project is located in
/ ~/development/clientmgntsystem_project/.

I had no issues the last time I ran 'python manage.py migrate' but today I
see that manage.py cannot find the installed django and asks if I have a
virtual environment. I do not because I have not seen my need for these.

Rather than try to push water uphill, I'll install both virtualenv and
virtualenvwrapper using the SlackBuilds.org packages.

My question is how to migrate both django and my project to the new
virtual environment.

Rich

[Alceu Rodrigues de Freitas Junior]

I guess you don't need to do anything besides running "source <whatever>/bin/activate" to use your new virtualenv ("whatever" should be directory where it is located).

[Antonis Christofides]

Hi,

once you understand what virtualenv does, it should be obvious. And virtualenv
is really quite simple. This should help:
https://djangodeployment.com/2016/11/01/virtualenv-demystified/

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com