Nebucatnetzer
/
network_inventory
mirror of https://github.com/Nebucatnetzer/network_inventory.git
1
0
Fork 0
Code Issues Releases Wiki Activity
470 Commits 10 Branches 4 Tags 9.4 MiB
CSS 51.7%
Python 34.4%
HTML 8.7%
JavaScript 3.2%
Nix 1.1%
Other 0.9%
Go to file
Andreas Zweili dcc3e39914 restructure the project 
Make the file tree a bit flatter in order to make the project less confusing
 		2020-01-07 18:10:57 +01:00
docs change the license model to be abstract 2019-12-29 19:00:47 +01:00
inventory restructure the project 2020-01-07 18:10:57 +01:00
network_inventory restructure the project 2020-01-07 18:10:57 +01:00
requirements change the RAID model so that it uses django-nested-admin 2019-12-27 18:28:30 +01:00
static/admin restructure the project 2020-01-07 18:10:57 +01:00
.coveragerc move the coverage config 2019-08-11 20:38:37 +02:00
.gitignore add a temp file to mark the first run 2019-08-10 15:03:03 +02:00
Dockerfile split the requirements and settings 2019-07-13 12:37:58 +02:00
LICENSE Initial commit 2017-12-21 23:11:33 +01:00
Makefile restructure the project 2020-01-07 18:10:57 +01:00
README.md remove outdated documentation 2019-08-30 23:22:19 +02:00
docker-compose.yml move some settings to environment variables 2019-08-28 21:39:29 +02:00
manage.py restructure the project 2020-01-07 18:10:57 +01:00
production.sh restructure the project 2020-01-07 18:10:57 +01:00
pytest.ini disable pytest legacy message for junit 2019-11-30 13:31:43 +01:00
run.sh restructure the project 2020-01-07 18:10:57 +01:00

README.md

network_inventory

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
  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.

Local Setup

  1. Run make local to create the virtual environment for development. You're now all set to start developing.

Docker Setup

  1. Run make to start the development server. You can access it at http://localhost:8000 . You're now all set to start developing.
    If you need to run migrations you can simply restart the Docker container.

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.

Todos

  • Create an Nginx configuration
  • extend the CSS
    • A more centered layout would be nice
    • Maybe some colours
  • include a RAID calculator
  • calculate the used space on a host Means calculate the size all the VMs would use if they were thick.