Feature Request: Automatically create router.db on first run if not present

[twille007]

Description

Currently, after installing and running Oxidized for the first time, users are required to manually create the router.db file before the service can function properly. While this makes sense when the goal is to backup configurations from systems, I believe it would improve the user experience if Oxidized automatically created an empty router.db file upon first execution if one does not already exist.

This would allow Oxidized to run smoothly right after installation, even if no devices have been configured yet. The service would be functional, though it would not actually back up any configurations until the user manually populates the router.db. This change could make the installation process more seamless and reduce potential friction for first-time users.

Proposed Solution

• On the first run of Oxidized, check for the existence of router.db.
• If the file is missing, automatically create an empty router.db.
• Log a message to inform the user that the file has been created and that they need to add devices for backups.