storj/satellite
Michal Niewrzal f731267e8c Per-project usage limiting (#2036)
What: Changes to support custom usage limit for the project. With this implementation by default project usage limit is taken from configuration flag. If project DB field usage_limit will be set to value larger than 0 it will become custom usage limit and we will be used to verify is limit was exceeded.

Whats changed:

usage_limit (bigint) field added to projects table (with migration)
things related to project usage moved from metainfo endpoint to project usage type
accounting.ProjectAccounting extended with GetProjectUsageLimits() method
Why: We need to have different usage limits per project. https://storjlabs.atlassian.net/browse/V3-1814
2019-05-28 09:36:52 -06:00
..
console Per-project usage limiting (#2036) 2019-05-28 09:36:52 -06:00
inspector moved invalid/offline back into SQL (#1838) 2019-05-01 09:45:52 -04:00
mailservice satellite/mailservice: wait for goroutines to finish (#1985) 2019-05-17 14:29:35 +02:00
metainfo Per-project usage limiting (#2036) 2019-05-28 09:36:52 -06:00
orders add Reverify to auditing (#2041) 2019-05-27 14:13:47 +03:00
satellitedb Per-project usage limiting (#2036) 2019-05-28 09:36:52 -06:00
peer.go Per-project usage limiting (#2036) 2019-05-28 09:36:52 -06:00