@atripp Thank you for this information. To clarify, you're suggesting that the temp folder for buffering uploads is actually the proget's iis service account temp folder?
If so that makes things simple to move, as you suggested.
Thanks
Kenneth Garza
@atripp Thank you for this information. To clarify, you're suggesting that the temp folder for buffering uploads is actually the proget's iis service account temp folder?
If so that makes things simple to move, as you suggested.
Thanks
Kenneth Garza
Heya,
So i am using the s3 backend for all of my feeds. Recently packages stopped uploading to the server to find that the disk for the server was full. (it was IIS logs, not related to proget).
It makes sense that when a package is uploaded to Proget its first stored on the local disk before synced to the s3 bucket. However, the concern is that this temp storage area is on the OS drive. I'd like to move this to a data drive.
I looked in the Administration -> Advanced settings to see if there was an obvious setting for this but does not appear so.
I am currently using Version 6.0.15 (Build 2)
Thanks
Kenneth Garza
@kenneth-garza_2882 Actually as an afterthought I looked up webooks and found they might be better for my usecases.
I am still interested in better docs for proget extensions though.
Hello, I am looking to write an extension for vulnerability scanning to integration into our preferred scanning software. I have already written a way to do this through github but we want to be able to do it through proget at well.
However it seems the Inedo.SDK documentation on what the classes are, how to use them are sorely lacking. Perhaps I am just really bad at finding good examples... but is there better documentation on how to create extensions.
I have a few use cases I would like to explore.
When new package is uploaded, the extension triggers a scan with our thirdparty software (through their api) and then reports the vulnerability state to proget.
when a prerelease package is promoted to full-release, i would like to move that package to another feed, and then make an API call to our Octopus Deploy server to create a release.
When a package is put into a certain feed, a event is triggered in which that package is automatically pushed to another proget server (in another cloud region, cannot connect them due to network issues)
is this possible with extensions? Are there better ways, such as webhooks we can setup? Thanks in advance.
Kenneth Garza