Go to file
Oliver ab4b91cd46 Added pages for /supplier/
- Supplier list view
- Supplier detail view /supplier/<pk>/
- Added create / edit / delete views for supplier
- Supplier part detail at /supplier/part/<pk>
- Added create / edit / delete views for supplier part
- Added some templates to make things easier
2018-04-15 15:35:01 +10:00
images/logo Updated breadcrumbs to use bootstrap 2018-04-14 23:42:24 +10:00
InvenTree Added pages for /supplier/ 2018-04-15 15:35:01 +10:00
requirements Added ability to edit parts 2018-04-15 01:18:12 +10:00
.gitattributes Added gitattributes file 2017-03-29 23:45:27 +11:00
.gitignore Added migration files to git index 2018-04-14 18:36:06 +10:00
.travis.yml Making sure travis has the build.txt requirements 2017-04-10 23:15:11 +02:00
LICENSE Initial commit 2017-03-23 12:44:10 +11:00
Makefile Update makefile 2018-04-12 18:57:25 +10:00
README.md Update README.md 2018-04-12 19:09:18 +10:00
roadmap.md Update roadmap.md 2017-04-02 23:46:00 +10:00
setup.cfg Modernized environment 2017-04-10 22:55:25 +02:00

License: MIT Build Status

InvenTree

InvenTree is an open-source Inventory Management System which provides powerful low-level stock control and part tracking. The core of the InvenTree system is a Python/Django database backend which provides an admin interface (web-based) and a JSON API for interaction with external interfaces and applications.

Installation

It is recommended to set up a clean Python 3.4+ virtual environment first: mkdir ~/.env && python3 -m venv ~/.env/InvenTree && source ~/.env/InvenTree/bin/activate

You can then continue running make setup (which will be replaced by a proper setup.py soon). This will do the following:

  1. Installs required Python dependencies (requires pip, should be part of your virtual environment by default)
  2. Performs initial database setup
  3. Updates database tables for all InvenTree components

This command can also be used to update the installation if changes have been made to the database configuration.

To create an initial user account, run the command make superuser.

Documentation

For project code documentation, refer to the online documentation (auto-generated)

Coding Style

If you'd like to contribute, install our development dependencies using make develop. All Python code should conform to the PEP 8 style guide. Run make style which will compare all source (.py) files against the PEP 8 style. Tests can be run using make test.