title: pipenv: deployment workflow
body: <p>I am thinking about switching from pip &amp; virtualenv to pipenv.  But after studying the documentation I am still at a loss on how the creators of pipenv structured the deployment workflow.</p>
  
  <p>For example, in development I have a <code>Pipfile</code> &amp; a <code>Pipfile.lock</code> that define the environment.  Using a deployment script I want to deploy</p>
  
  <ol>
  <li><code>git pull</code> via Github to production server</li>
  <li><code>pipenv install</code> creates/refreshes the environment in the home directory of the deployment user</li>
  </ol>
  
  <p>But I need a venv in a <strong>specific</strong> directory which is already configured in systemd or supervisor.  E.g.: <code>command=/home/ubuntu/production/application_xy/env/bin/gunicorn module:app</code></p>
  
  <p>pipenv creates the env in some location such as 
  <code>/home/ultimo/.local/share/virtualenvs/application_xy-jvrv1OSi</code></p>
  
  <p><strong>What is the intended workflow to deploy an application with <code>pipenv</code>?</strong></p>