Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
Changes the file structure of the repo a bit, to make it more like recent LIL projects. Notably, one of the directories named
perma-payments
is now namedweb
. I did NOT change the Django app fromperma_payments
to our now-usualmain
, because that would have required extensive changes across most files, and would affect the db and migrations; I don't think it's worth it.Switches from pipenv to pip-tools, and, to facilitate that, switches the base Docker image from plain
debian:buster
topython:3.7-buster
Upgrades to Django 2.2. (I stopped there, rather than going all the way to Django 3.0 or 3.1, because 2.2 is the current LTS version, and Jack recommends sticking with those.)
Upgrades the rest of python packages
The changes to the file structure and the move to pip-tools will certainly require changes to our deployments and deployment scripts... I think it's worth it, so that, after I similarly alter Perma, all our projects use pip-tools.