#256 Migrate all project dependencies to Pipfile
Merged by jflory7. Opened by jflory7.
fedora-commops/ jflory7/fedora-happiness-packets change/pipenv  into  master

Download 256.patch

This PR reworks how our project dependencies are managed. Instead of the requirements.txt files, this uses a single Pipfile to manage "production" and "development" dependencies for the project. See commit messages below for details:

commit d810b1f52d11b3eea2c5e88a3cc1311089c38d28
Date: Fri Jun 28 21:57:16 2019 -0500

dependencies: Migrate docs deps to root directory
This is a first step in migrating all project dependencies to Pipenv.
This commit specifically adds the docs dependencies into a new Pipfile
specified at the root of the project.

commit 942aa2800a11a1d0131601bd43e52b26d51daa1f
Date: Mon Jul 1 22:48:52 2019 -0500

Migrate all project dependencies to Pipfile
This commit removes the multiple requirements.txt files used to install
and manage dependencies and opts in favor of the Pipfile managed by
Pipenv:
    https://github.com/pypa/pipfile
    https://pipenv.org/
The purpose of this change is to maintain DRY principles. This makes our
dependencies easier to manage by managing them in one place and only
dividing them by standard dependencies or development dependencies.
Future changes after this commit will include documentation improvements
and updates to the Dockerfile to install dependencies in the Pipfile
format.

commit d7ac81f5b6cfbe293684e08921f4ddc5e3375dc1
Date: Mon Jul 1 23:03:03 2019 -0500

Refactor Dockerfile, use pipenv for Python packages
This commit refactors the Dockerfile to use fewer layers when building
the image. It also re-arranges the order of how things are run to
benefit some steps like installing Python dependencies.
Ultimately, this commit leverages Pipenv for managing and installing
dependencies within the project. This is one additional change to
improving awareness of dependencies and ensuring development,
production, and staging will always use the same set of dependencies.

commit f10b2447dd2fd1e07defc802f5c0dcceb5d8ad33
Date: Mon Jul 1 23:14:58 2019 -0500

Dockerfile: Install development dependencies
This is not sustainable and not recommended. But in practice, this is
the same as we were doing before. I wonder if it's better to have a prod
and dev Dockerfile with different Django settings and Pipenv flags.

Metadata Update from @jflory7:
- Pull-request tagged with: needs testing, new change, type - infra, type - internal organization

Oops, I forgot to update the docs. Going to hold off on this one for now until I have a chance to update them accordingly.

Metadata Update from @jflory7:
- Pull-request untagged with: needs testing
- Pull-request tagged with: needs changes, type - docs
- Request assigned

1 new commit added

  • Add pytest-mock to devel dependencies

rebased onto 1ce0b0670f22b7e6fe2ea9f64ce8fe170b11f118

rebased onto d146cd9abded3ca170fa8bd5f8795bcfe8da3f0e

Pull-Request has been merged by jflory7