You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
Related to #34. Since you are thinking about enhancements to the structures, I'd like to throw one more suggestion to consider.
Sometimes a large block owned by a hosting provider may contain few smaller blocks designated for other data centers or even other clients who potentially use the addresses for other purposes (i.e. offices, individual customers, whatever). The current structure of datacenters.csv is not a good fit to express such data.
One of the possible workarounds is the format used by Nginx for its geo module. It's possible not only to "include" a block, but also mark a block as "excluded". Here it is the module documentation if you'd want to see it.
The text was updated successfully, but these errors were encountered:
Related to #34. Since you are thinking about enhancements to the structures, I'd like to throw one more suggestion to consider.
Sometimes a large block owned by a hosting provider may contain few smaller blocks designated for other data centers or even other clients who potentially use the addresses for other purposes (i.e. offices, individual customers, whatever). The current structure of
datacenters.csv
is not a good fit to express such data.One of the possible workarounds is the format used by Nginx for its
geo
module. It's possible not only to "include" a block, but also mark a block as "excluded". Here it is the module documentation if you'd want to see it.The text was updated successfully, but these errors were encountered: