inventree/inventree-docs
2
0
Fork 0
mirror of https://github.com/inventree/inventree-docs.git synced 2025-04-28 05:36:46 +00:00
Code
inventree-docs/docs/faq.md
Oliver b2f91886b9
Update faq.md 
Add warning about invoke update
2022-06-25 11:08:37 +10:00

2.4 KiB
Raw Blame History

title
title
FAQ

Frequently Asked Questions

Errors during InvenTree update

Sometimes, users may encounter unexpected error messages when updating their InvenTree installation to a newer version.

The most common problem here is that the correct sequenct of steps has not been followed:

  1. Ensure that the InvenTree web server and background worker processes are halted
  2. Update the InvenTree software (e.g. using git or docker, depending on installation method)
  3. Run the invoke update command
  4. Restart the web server and background worker processes

For more information, refer to the installation guides:

!!! warning "Invoke Update" You must ensure that the invoke update command is perfomed every time you update InvenTree

Feature x is not visible after update

If a particular menu / item is not visible after updating InvenTree, it may be due to your internet browser caching old versions of CSS and JavaScript files.

Before raising an issue, try hard-refreshing the browser cache:

Ctrl + Shift + R

or

Ctrl + F5

Problems Installing on Windows

InvenTree installation is not officially supported natively on Windows. Install using the WSL framework.

Command 'inv' / 'invoke' not found

If the inv or invoke command does not work, it means that the invoke python library has not been correctly installed.

Update the installed python packages with PIP:

pip3 install -U -r requirements.txt

ModuleNotFoundError: No module named 'django'

Most likely you are trying to run the InvenTree server from outside the context of the virtual environment where the required python libraries are installed.

Always activate the virtual environment before running server commands!

Background Worker "Not Running"

The background worker process must be started separately to the web-server application.

From the top-level source directory, run the following command from a separate terminal, while the server is already running:

invoke worker

!!! info "Supervisor" A better option is to manage the background worker process using a process manager such as supervisor. Refer to the production server guide.