Private key limit too low for keeping mirror updated?
Posted: Mon Mar 01, 2021 3:04 pm
Hey,
I know that you recommend setting up a mirror once using the JSON-dump of the database and then using the public key to have users update their data.
However, I was thinking to run my own mirror and keep it updated, while having users contact my own API. This would also reduce the load on your server.
So basically:
Lots of requests: My users -> My server
Only once or twice a day: my server -> your server
But when doing this, the private key will reach its limit within the first year of doing updates if I update daily. Is there any way around that or should I have users contact your API directly instead of mine?
I know that you recommend setting up a mirror once using the JSON-dump of the database and then using the public key to have users update their data.
However, I was thinking to run my own mirror and keep it updated, while having users contact my own API. This would also reduce the load on your server.
So basically:
Lots of requests: My users -> My server
Only once or twice a day: my server -> your server
But when doing this, the private key will reach its limit within the first year of doing updates if I update daily. Is there any way around that or should I have users contact your API directly instead of mine?