Get ready to contribute to LibreNMS
This document is intended to help you get your local environment set up to contribute code to the LibreNMS project.
Setting up a development environment
When starting to develop, it may be tempting to just make changes on your production server, but that will make things harder for you. Taking a little time to set up somewhere to work on code changes can really help.
Possible options: * A Linux computer, VM, or container * Another directory on your LibreNMS server * Windows Subsystem for Linux
Set up your development git clone
- Follow the documentation on using git
- Install development dependencies
- Set variables in .env, including database settings. Which could be a local or remote MySQL server including your production DB.
APP_ENV=local APP_DEBUG=true ...
- Start a development webserver
- Access the Web UI at http://localhost:8000
LibreNMS uses continuous integration to test code changes to help reduce bugs. This also helps guarantee the changes you contribute won't be broken in the future. You can find out more in our Validating Code Documentation
Polling debug output
You can see detailed info by running your polling code in debug mode. If you are looking at a specific
./discovery.php -d -h HOSTNAME ./poller.php -d -h HOSTNAME
Sometimes you want to find out what a variable contains (such as the data return from an snmpwalk). You can dump one or more variables and halt execution with the dd() function.
Inspecting web pages
Installing the development dependencies and setting APP_DEBUG enables the Laravel Debugbar This will allow you to inspect page generation and errors right in your web browser.
Better code completion in IDEs and editors
You can generate some files to improve code completion. (These file are not updated automatically, so you may need to re-run these command periodically)
./lnms ide-helper:generate ./lnms ide-helper:models -N
You can find a lot of how LibreNMS works by following the Laravel Documentation