Edward Kirton wrote:
also, delete and purge a quota seems to have no effect.
Hi Ed,
They work for me. Note that delete/purge do not actually delete the db row itself.
Delete marks the quota as deleted, and it no longer counts against any associated users. Purge removes all of the user/group associations, but it still remains in the database.
If this isn't what you're seeing, can you send more details?
Thanks for testing out new features! --nate
On Wed, Aug 24, 2011 at 3:58 PM, Edward Kirton eskirton@lbl.gov wrote:
i created some quotas which were assigned to groups (set as for "yes, registered users") but apparently the groups didn't initially stick; i had to edit the quota after creation to reassign the group.
On Fri, Aug 19, 2011 at 4:44 PM, Jennifer Jackson jen@bx.psu.edu wrote:
Galaxy public instances: data and job quotas
User data and job quota limits are now implemented at the public Galaxy Test instance http://test.g2.bx.psu.edu:
http://galaxyproject.org/Test#**Quotashttp://galaxyproject.org/Test#Quotas
While no quotas are currently implemented at the public Galaxy Main instance http://usegalaxy.org, we do ask that users stay within certain usage limits:
http://galaxyproject.org/Main#**Quotashttp://galaxyproject.org/Main#Quotas
If you find that you require additional resources, please consider the alternative Galaxy options explained at:
http://galaxyproject.org/Big%**20Picture/Choiceshttp://galaxyproject.org/Big%20Picture/Choices
Thanks for using Galaxy! ______________________________**_____________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: