I move all todos to the Github Issues.
|13 hours ago|
|.vscode||2 months ago|
|backups||6 days ago|
|computers||6 days ago|
|core||2 weeks ago|
|customers||3 weeks ago|
|devices||3 weeks ago|
|docs||13 hours ago|
|licenses||6 days ago|
|nets||3 weeks ago|
|network_inventory||2 months ago|
|nginx||4 months ago|
|requirements||2 weeks ago|
|softwares||3 weeks ago|
|users||3 weeks ago|
|.coveragerc||4 months ago|
|.dir-locals.el||2 months ago|
|.env-example||4 months ago|
|.flake8||4 months ago|
|.gitignore||2 months ago|
|.travis.yml||4 months ago|
|Dockerfile||1 day ago|
|LICENSE||2 years ago|
|Makefile||1 day ago|
|README.md||13 hours ago|
|conftest.py||3 months ago|
|docker-compose-development.yml||1 day ago|
|docker-compose.yml||1 day ago|
|manage.py||6 months ago|
|network_inventory.yaml||2 weeks ago|
|pytest.ini||2 months ago|
|run.sh||1 day ago|
I started this project in order to have solution for keeping an inventory over my various servers and other network equipment.
.envand change the
DJANGO_SECRET_KEYvariables to something secure.
docker-compose upand connect to http://localhost
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.
make localto create the virtual environment for development. You’re now all set to start developing.
This is very similar to the production setup with the difference that the image
web application gets built locally instead of getting pulled from
maketo start the server. You can access it at http://localhost . You’re now all set to start working.
make initafter you successfully run
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.
Currently there isn’t a lot of documentation present. I try to document my thoughts and other related information in the Notes file.