Apply renovate patches and update the project to support netbox-docker 3.0.1

[jsenecal]

Breaking changes

• Removal of the now unsupported netbox_napalm_* variables
• Uses valkey instead of redis due to licence changes

Features

• Replaces netbox_proxy_network_name (a string) with netbox_additionnal_network_names (a list) to allow for different scenarios
• Updates the docker-compose file to add upstream health checks.

Fixes #16 and #6

[jsenecal]

Is there something about the new Redis license that makes it incompatible with this project, or this project's license? Many of us rely on the stability and proven history of Redis in production workloads, and aren't yet ready to move to another offering that has not yet had ample time to prove it's development practices and stewardship. If there is an incompatibility, I'm of course happy to honor licenses and commit to removing Redis from this project, but if it's just preference- I'd prefer keeping things as they are, or perhaps exploring an option that would let the end user opt for Redis or Valkey as it fits their goals.

Under the new license, cloud service providers hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge. For example, cloud service providers will be able to deliver Redis 7.4 only after agreeing to licensing terms with Redis, the maintainers of the Redis code. These agreements will underpin support for existing integrated solutions and provide full access to forthcoming Redis innovations.

This also means that a service provider cannot freely distribute a solution with a Redis component under this new licensing.

Valkey is a FOSS fork of Redis backed by the Linux Foundation.

This change also follows upstream decision to move away from Redis. https://github.com/netbox-community/netbox-docker/pull/1203

[wastrachan]

Is there something about the new Redis license that makes it incompatible with this project, or this project's license? Many of us rely on the stability and proven history of Redis in production workloads, and aren't yet ready to move to another offering that has not yet had ample time to prove it's development practices and stewardship. If there is an incompatibility, I'm of course happy to honor licenses and commit to removing Redis from this project, but if it's just preference- I'd prefer keeping things as they are, or perhaps exploring an option that would let the end user opt for Redis or Valkey as it fits their goals.

Under the new license, cloud service providers hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge. For example, cloud service providers will be able to deliver Redis 7.4 only after agreeing to licensing terms with Redis, the maintainers of the Redis code. These agreements will underpin support for existing integrated solutions and provide full access to forthcoming Redis innovations.

This also means that a service provider cannot freely distribute a solution with a Redis component under this new licensing.

Valkey is a FOSS fork of Redis backed by the Linux Foundation.

This change also follows upstream decision to move away from Redis. netbox-community/netbox-docker#1203

Thanks, this is helpful. I generally undestand the ramifications of the new license-- but knowing that Netbox has switched offers me at least the assurance that Nextbox will be continuously tested with Valkey.