mirror of
https://github.com/kennethreitz/pipenv.git
synced 2026-06-05 22:50:18 +00:00
+7
-1
@@ -257,7 +257,7 @@ the current working directory when working on packages::
|
||||
Note that all sub-dependencies will get added to the ``Pipfile.lock`` as well.
|
||||
|
||||
|
||||
☤ Managing System Dependencies
|
||||
☤ Deploying System Dependencies
|
||||
------------------------------
|
||||
|
||||
You can tell Pipenv to install things into it's parent system with the ``--system`` flag::
|
||||
@@ -266,6 +266,12 @@ You can tell Pipenv to install things into it's parent system with the ``--syste
|
||||
|
||||
This is useful for Docker containers, and deployment infrastructure (e.g. Heroku does this).
|
||||
|
||||
Also useful for deployment is the ``install --deploy`` flag:
|
||||
|
||||
$ pipenv install --system --deploy
|
||||
|
||||
This will fail a build if the lockfile is out–of–date, instead of genreating a new one.
|
||||
|
||||
|
||||
☤ Generating a ``requirements.txt``
|
||||
-----------------------------------
|
||||
|
||||
Reference in New Issue
Block a user