Keeping Netbox RIPE Updater current means pulling the latest code, rebuilding the Docker image, and periodically rotating RIPE API credentials. RIPE enforces a 12-month maximum TTL on API keys, so credential rotation is a recurring operational task — not a one-off step.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/jalmargyyk/netbox-ripe-updater/llms.txt
Use this file to discover all available pages before exploring further.
This project follows Semantic Versioning. Minor and patch releases are safe to apply without reviewing breaking changes. A major version bump signals breaking changes — read the GitHub release notes before upgrading across a major boundary.
Updating the containers
Pull the desired version
Choose whether you want the latest commit on the current branch or a specific tagged release.
- Latest version
- Specific release
Rebuild the containers
Always rebuild after pulling new code. The Docker image is built from source, so a rebuild is required to include any Python or Dockerfile changes.
Rotating RIPE API keys
RIPE imposes a maximum TTL of 12 months on API keys. Set a calendar reminder so you rotate credentials before they expire — an expired key causes the updater to silently fail to push objects to RIPE.Manual rotation
UpdateRIPE_API_USER and RIPE_API_PASS in .env.updater, then restart the containers:
Automated rotation with update-ripe-key.sh
A helper script is included at./update-ripe-key.sh. It prompts for the new credentials, backs up .env.updater with a timestamp, updates the values in-place, and restarts the containers automatically.
update-ripe-key.sh
.env.updater (e.g. .env.updater.bak.20250517_143022) before making any changes, so you can roll back by copying the backup file back and restarting.
Deployment
Review the full Docker Compose setup and port configuration
Backups
Browse and restore backed-up RIPE objects