Skip to content

Update frequency references database release schedule #319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 12, 2024

Conversation

christophermluna
Copy link
Contributor

No description provided.

[database release schedule](https://support.maxmind.com/hc/en-us/articles/4408216129947-Download-and-Update-Databases#h_01G3XX402XKD3J1CMWKNKMDYYZ)
for more information.

On most Unix-like systems, this can be achieved by using cron. Below is a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While giving an example crontab is helpful, it is problematic because end users will copy and paste the crontab, resulting in multiple users hitting our servers at the exact same time.

A possible solution is linking to the relevant section of the dev site: https://dev.maxmind.com/geoip/updating-databases#3-run-geoip-update
If you refresh the page, you'll see that the example crontab uses random days of the week and times while still ensuring that the days of the week are spaced out enough to fall within the twice weekly database update.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool, i didn't realize the dev portal did that. updated

- link to the dev portal for a randomized crontab file to avoid many users hitting the update at the same day/time
@christophermluna christophermluna merged commit fd445c7 into main Jun 12, 2024
17 checks passed
@christophermluna christophermluna deleted the cluna/change-frequency-of-updates-in-docs branch June 12, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants