InvenTree/Makefile
Diego Herranz 518fb78077 Makefile: add .PHONY targets
Given all the targets are actions instead of files to be generated,
.PHONY should be used, mainly to avoid a conflict with a file of the same name.

See https://www.gnu.org/software/make/manual/html_node/Phony-Targets.html
2019-08-02 06:45:01 +01:00

50 lines
1.3 KiB
Makefile

clean:
find . -path '*/__pycache__/*' -delete
find . -type d -name '__pycache__' -empty -delete
find . -name *.pyc -o -name *.pyo -delete
rm -rf *.egg-info
rm -rf .cache
rm -rf .tox
rm -f .coverage
migrate:
python3 InvenTree/manage.py makemigrations company
python3 InvenTree/manage.py makemigrations part
python3 InvenTree/manage.py makemigrations stock
python3 InvenTree/manage.py makemigrations build
python3 InvenTree/manage.py makemigrations order
python3 InvenTree/manage.py migrate --run-syncdb
python3 InvenTree/manage.py check
requirements:
pip3 install -U -r requirements.txt
secret:
python3 InvenTree/keygen.py
superuser:
python3 InvenTree/manage.py createsuperuser
install: requirements secret migrate superuser
style:
flake8 InvenTree
test:
python3 InvenTree/manage.py check
python3 InvenTree/manage.py test build company part stock order
coverage:
python3 InvenTree/manage.py check
coverage run InvenTree/manage.py test build company part stock order InvenTree
coverage html
documentation:
pip3 install -U -r docs/requirements.txt
cd docs & make html
backup:
python3 InvenTree/manage.py dbbackup
python3 InvenTree/manage.py mediabackup
.PHONY: clean migrate requirements secret superuser install style test coverage documentation backup