2019-06-10 20:59:46 +02:00
|
|
|
# network_inventory
|
|
|
|
|
|
2020-01-07 18:16:29 +01:00
|
|
|
[](https://travis-ci.com/Nebucatnetzer/network_inventory)
|
|
|
|
|
|
2019-06-10 20:59:46 +02:00
|
|
|
I started this project in order to have solution for keeping an
|
|
|
|
|
inventory over my various servers and other network equipment.
|
|
|
|
|
|
|
|
|
|
## Setup
|
|
|
|
|
|
|
|
|
|
1. Clone the repository
|
2019-07-13 15:25:32 +02:00
|
|
|
2. Now decide if you want to develop fully locally or inside the docker
|
|
|
|
|
container. Locally you'll use SQlite for the database and inside the Docker
|
|
|
|
|
container you'll use Postgres for the database. For the moment there aren't
|
|
|
|
|
any features implemented which require Postgres. However this might change
|
|
|
|
|
in the future and SQlite is not supported for production.
|
2020-02-15 15:25:54 +01:00
|
|
|
3. Copy the `.env-example` file to `.env` and change the `POSTGRES_PASSWORD`
|
|
|
|
|
and `DJANGO_SECRET_KEY` variables to something secure.
|
2019-07-13 15:25:32 +02:00
|
|
|
|
|
|
|
|
### Local Setup
|
2020-04-27 22:43:14 +02:00
|
|
|
|
|
|
|
|
The local setup is mainly intended to run the tests quickly. I recommend that
|
|
|
|
|
you use the Docker setup if you want to interact with the website.
|
|
|
|
|
|
2020-02-15 15:25:54 +01:00
|
|
|
4. Run `make local` to create the virtual environment for development.
|
2019-08-28 21:32:16 +02:00
|
|
|
You're now all set to start developing.
|
2019-06-10 20:59:46 +02:00
|
|
|
|
2019-07-13 15:25:32 +02:00
|
|
|
### Docker Setup
|
2020-04-27 22:43:14 +02:00
|
|
|
|
|
|
|
|
4. Run `make` to start the production server. You can access it
|
|
|
|
|
at http://localhost . You're now all set to start working.
|
|
|
|
|
5. If you want to develop with the Docker setup change the `run` command in the
|
|
|
|
|
`docker-compose.yml` from `run.sh` to `development.sh`
|
2019-06-10 20:59:46 +02:00
|
|
|
|
2019-08-28 21:32:16 +02:00
|
|
|
#### Environment Variables
|
|
|
|
|
|
|
|
|
|
To customise the application in the Docker container you can use environment
|
|
|
|
|
variables in the docker-compose.yml file. Currently the following variables are
|
|
|
|
|
supported.
|
|
|
|
|
|
|
|
|
|
- **DJANGO_SECRET_KEY** the secret key is mandatory, otherwise the application
|
|
|
|
|
doesn't run. Make sure that it is some long random string.
|
|
|
|
|
- **DJANGO_DEBUG** settings this variable to any value enables the Django debug
|
|
|
|
|
mode. Make sure that you don't set it on a production server.
|
|
|
|
|
- **DJANGO_SETTINGS_MODULE** the path to the settings file to use in the
|
|
|
|
|
container. This requires a dotet syntax. The default is
|
|
|
|
|
`network_inventory.settings.docker`.
|
