# Django project within virtual environment or shared common folder **URL:** \ **Category:** Getting Started\ **Created:** [August 9, 2023, 7:56pm UTC](https://forum.djangoproject.com/t/django-project-within-virtual-environment-or-shared-common-folder/22930 "2023-08-09T19:56:47Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\ **Post date:** [August 9, 2023, 8:24pm UTC](https://forum.djangoproject.com/t/django-project-within-virtual-environment-or-shared-common-folder/22930/2 "2023-08-09T20:24:36Z")
I most commonly see two patterns being used in practice and discussed here. Some people put their virtual environment within their project. That way, when they deploy their project, the entire virtual environment is deployed along with it. That’s also how they manage their virtual environments and know exactly which environment is being used with which project. Other people, myself being one of them, keep a separate directory for my virtual environments from my projects. The virtual environments all reside within a directory named “ve” and the projects reside in other, different directories not physically related to “ve”. By creating and deploying a separate “ve” directory, I can then deploy a variety of projects that all use that same virtual environment. I’m not aware of anyone putting their Django project directory inside the “ve”. I’m guessing you could do it, I just haven’t seen it done. But for the most part, the choice between these options is made on the basis of factors _other_ than purely technical issues. Django itself doesn’t care. --- _[View the full topic](https://forum.djangoproject.com/t/django-project-within-virtual-environment-or-shared-common-folder/22930)._