-
Notifications
You must be signed in to change notification settings - Fork 0
/
Makefile
99 lines (70 loc) · 3 KB
/
Makefile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
# This Makefile is based on the Makefile defined in the Python Best Practices repository:
# https://git.datapunt.amsterdam.nl/Datapunt/python-best-practices/blob/master/dependency_management/
#
# VERSION = 2020.01.29
.PHONY: help pip-tools install requirements update test init
UID:=$(shell id --user)
GID:=$(shell id --group)
dc = docker compose
run = $(dc) run --rm -u ${UID}:${GID}
manage = $(run) dev python manage.py
help: ## Show this help.
@fgrep -h "##" $(MAKEFILE_LIST) | fgrep -v fgrep | sed -e 's/\\$$//' | sed -e 's/##//'
pip-tools:
pip install pip-tools
install: pip-tools ## Install requirements and sync venv with expected state as defined in requirements.txt
pip-sync requirements.txt requirements_dev.txt
requirements: pip-tools ## Upgrade requirements (in requirements.in) to latest versions and compile requirements.txt
## The --allow-unsafe flag should be used and will become the default behaviour of pip-compile in the future
## https://stackoverflow.com/questions/58843905
pip-compile --upgrade --output-file requirements.txt --allow-unsafe requirements.in
pip-compile --upgrade --output-file requirements_dev.txt --allow-unsafe requirements_dev.in
upgrade: requirements install ## Run 'requirements' and 'install' targets
build: ## Build docker image
$(dc) build
push: build ## Push docker image to registry
$(dc) push
push_semver:
VERSION=$${VERSION} $(MAKE) push
VERSION=$${VERSION%\.*} $(MAKE) push
VERSION=$${VERSION%%\.*} $(MAKE) push
clean: ## Clean docker stuff
$(dc) down -v --remove-orphans
app:
$(dc) up app
# the name option is explicitly set, so the back- and frontend can communicate
# with eachother while on the same docker network. The frontend docker-compose
# file contains a reference to the set name
dev: migrate
$(run) --name bereikbaarheid-backend-django-dev --service-ports dev
test: lint ## Execute tests
$(run) test pytest $(ARGS)
loadtest: migrate
$(manage) make_partitions $(ARGS)
$(run) locust $(ARGS)
test_data:
$(manage) generate_test_data --num_days 25 --num_rows_per_day 2000
pdb:
$(run) dev pytest --pdb $(ARGS)
bash:
$(run) dev bash
shell:
$(manage) shell_plus
dbshell:
$(manage) dbshell
migrate:
$(manage) migrate
migrations:
$(manage) makemigrations $(ARGS)
trivy: ## Detect image vulnerabilities
$(dc) build --no-cache app
trivy image --ignore-unfixed docker-registry.secure.amsterdam.nl/datapunt/bereikbaarheid-backend
lintfix: ## Execute lint fixes
$(run) test black /src/$(APP) /tests/$(APP)
$(run) test autoflake /src --recursive --in-place --remove-unused-variables --remove-all-unused-imports --quiet
$(run) test isort /src/$(APP) /tests/$(APP)
lint: ## Execute lint checks
$(run) test autoflake /src --check --recursive --quiet
$(run) test isort --diff --check /src/$(APP) /tests/$(APP)
diff:
@python3 ./deploy/diff.py