Thanks, that is good to know on the counts! So per index seems fine for permissions managements.
Additionally, I'd like to do quite a few things within the devpiserver_on_upload hook. I understand that is still early in the development phase for that hook, but some of the things I'd like to be able to:
- automatically push certain packages up to our production index - send the package to a team city server for a regression test - somewhat tie a "package" to a particular list (related to my permissions issue) so that I know things are making it to the production list from the correct team.
I started a bit on that last one and tried using the stage.del_versiondata(), which is illegal since I'm within a transaction already. It seems that what I really need to do is spawn a thread that would issue a new transaction? I guess in general: what can I do within the "on_upload" hook? And any best-methods that folks would recommend for the "thread + transaction" that would allow me to use the functions that are available off of the stage object?
Any tips are greatly appreciated.
On Monday, January 26, 2015 at 4:56:52 AM UTC-5, Erb, Stephan wrote:
We have about 200 users and 800 indices on a devpi installation with 4 cores and 4 GB of RAM. Guess you will be ok even if you decide to do one index per package.
Is it be possible to somehow interject per package permissions control (within a single index) in to the current devpi setup? or is the only way to do that via a development index per package?
Even if it is a combo of both "auth_user" and "on_upload" hook that I would need to write...is it doable?
If not, I'm curious what is perhaps the most number of indexes folks have used? I'm pretty sure I would be hitting in to the hundreds (but probably not thousands).