4 ms·
Maybe I'm wrong(I hope I'm missing something, if I do please elaborate), but given the unpredictable behavior of package managers caching behavior and general d
by rjzzleep 7y ago
Maybe I'm wrong(I hope I'm missing something, if I do please elaborate), but given the unpredictable behavior of package managers caching behavior and general dynamic IPs the individual license is basically meaningless.
I can't even begin to imagine the headache and potential problems of having to deal with this. Isn't there a better way to handle supporting open source projects?
But other than that looks pretty with more or less clean execution.
- sdrzn 7y agoWe whitelist common dynamic IPs, for example CI, CD, and deployment IP address ranges including: * AWS * Heroku * GitHub * Circle CI (this whitelist is a WIP and I'm open to adding more) Also since the goal of rate limiting by IP is to limit # of users, not necessarily # of machines, we allow you to remove any previously used IP addresses from your subscription's history. This way if you hit your limit, just go to the payment page, hit 'Manage IPs' and remove any unused IPs. See this doc for more details: https://gitroyalty.com/docs/faq/how-do-subscriptions-work https://gitroyalty.com/docs/faq/how-do-subscriptions-work