Go to file
Andreas Zweili 02643a9e55 add the large version of the diagramm 2019-07-24 19:56:55 +02:00
docs add the large version of the diagramm 2019-07-24 19:56:55 +02:00
network_inventory remove the default test s file 2019-07-19 17:10:35 +02:00
requirements add rope to the development depencies 2019-07-19 16:09:06 +02:00
.gitignore change setup to docker 2019-06-10 20:59:46 +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 extend the "make local" command 2019-07-13 15:38:21 +02:00
README.md extend the "make local" command 2019-07-13 15:38:21 +02:00
Vagrantfile correct the vagrant file 2018-01-31 17:16:05 +01:00
docker-compose.yml Add a Makefile 2019-07-13 15:25:32 +02:00
run.sh Add a Makefile 2019-07-13 15:25:32 +02: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 start the development server. You can access it at http://localhost:8000 . 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.

Todos

  • Create an Apache configuration
  • configure htaccess or something similar
  • 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.
  • Move the lists to their own page. Since I have more devices than I thought it would provide a better overview than one big list.
  • Add a Counter to the RAM Modules
  • Create an abstract company class
  • Create Customer and a Manufacturer sub class Those two would be based on the company class. I'm currently not sure how I should handle the case where a company is both a customer and a manufacturer.
  • Create a NET category where a device can live in. This NET Category should display it's IP range, Subnet mask and show it's DHCP range if one is configured.
  • Create class DeviceInNet This class shows the relationship between the device and a NET. An attribute of a DeviceInNet should be an IP address.
  • Recreate the RM in draw.io The Dia RM is okay but not really that great. Draw.io would give a better result.

Developemenet

For a detailed documentation of the source have a look at the documentation.