2
0
mirror of https://github.com/inventree/inventree-docs.git synced 2025-06-12 10:15:33 +00:00

Update internal links to use relative pathing

This commit is contained in:
Oliver Walters
2020-10-19 11:15:31 +11:00
parent 521b2171f2
commit 9150675a56
13 changed files with 35 additions and 35 deletions

View File

@ -20,7 +20,7 @@ Database selection should be determined by your particular installation requirem
### Serving Data
Once a database is setup, you need a way of accessing the data. InvenTree provides a "server" application out of the box, but this may not scale particularly well with multiple users. Instead, InvenTree can be served using a webserver such as [Gunicorn](https://gunicorn.org/). For more information see the [deployment documentation](/start/deploy).
Once a database is setup, you need a way of accessing the data. InvenTree provides a "server" application out of the box, but this may not scale particularly well with multiple users. Instead, InvenTree can be served using a webserver such as [Gunicorn](https://gunicorn.org/). For more information see the [deployment documentation](./deploy).
## OS Requirements
@ -145,7 +145,7 @@ Once the required packages are installed, the database configuration must be adj
As part of the previous *install* step, a configuration file (**config.yaml**) is created. The configuration file provides administrators control over various setup options without digging into the Django *settings.py* script. The default setup uses a local sqlite database with *DEBUG* mode enabled.
For further information on installation configuration, refer to the [Configuration](/start/config) section.
For further information on installation configuration, refer to the [Configuration](../config) section.
!!! warning "Configure Database"
Ensure database settings are correctly configured in `config.yaml` before proceeding to the next step!
@ -190,4 +190,4 @@ This will launch the InvenTree web interface at `http://127.0.0.1:8000`. For oth
### Run Production Server
For a production install, refer to [deployment instructions](/start/deploy).
For a production install, refer to [deployment instructions](../deploy).