Hello Jonathan, We use Proget to deploy our PSModules. The deployement is driven with an Otter PSEnsure fonction- check if module exist with a specific version, if not deploy - Each new server is linked to an Otter role and after remediation, the module is installed. To update the module, we change version number in a otter variable. Otter remediation make the job We call PS function from local script or from Otter plan directly or from module. Don't know if this your need but it is working fine for us.

Ok, thank you!

HTTP should be about same speed as FTP; you'll most certainly need to use chunked uploads. But Asset directories don't support drop folders, and we don't have a reindexing function for asset directories. So unfortunately there's no supported way to handle this. You might be able to "hack" something by going to the database and filesystem directly, but we obviously can't recommend it.

Interesting; I know it's not ideal, but it works, and it may only be a slight inconvenience at best, since not many search for packages from the UI, I think. https://github.com/Inedo/inedo-docs/blob/master/ProGet/feeds/pypi.md If anyone finds more issues with this, please let us know and we can consider investing in a proper fix.

@tdean_3904 said in Error attempting to Tag a Docker Image: NETWORK SERVICE Following line needs to be added to daemon.json under Programdata\docker\config { "group" : "Network Service" }

Hi, Thanks for letting us know. Looks like the error message is wrong - actually the problem is caused by build metadata being present in a version number that is not a semver2 version. We've filed this as PG-1655 to make parsing these versions more permissive - it will be fixed in the next ProGet release (5.2.23), currently scheduled for Jan-17.

Hello @luminiscence_6236, It looks like ProGet is misinterpreting the auth token request helm sends during the second command as being anonymous. I've filed PG-1651 to address this.

Hello; this will probably be the fastest route to fix things -- https://docs.inedo.com/docs/desktophub/troubleshooting

Hi. Ah, thanks for the reminder about BaseUrl; I did have a hunt through advanced settings before posting here, but completely missed it. Still, good that you have updated the docs to reflect this - will hopefully save someone else some time. Cheers.

Hello @PhilippeC, I was able to reproduce this and I've filed OT-362 to fix this.

@atripp Thanks for the clarification, you have me pointed to the tooling and steps I will need to perform the bulk import. I will have to try, but I think I have enough information to script this task.

Hello @alan_2809, For this, I'd suggest using a third party reverse proxy such as Caddy, nginx, Apache, or HAProxy. That will have the added benefit of allowing you to host more than one HTTPS site on the same IP address. I'll update the documentation to give examples for each of these, but in the meantime, each one of the HTTP servers I suggested above has pretty good documentation for how to set them up as reverse proxies and how to set up TLS certificates.

I had the same issue. What seems to solve this is to add "static content" in IIS features link

Hello; here is more information about activation logic https://docs.inedo.com/docs/various/licensing/activation Maybe when you're offline, your network interface changes? I suppose in this case, you can just save your activation code in a text file, and swap it as you need?

Hello; most likely, you have a proxy in between ProGet and and PyPi.org. This can be configured under Admin > Proxy

@ben Thanks for the reply. I just upgraded to the latest version and it seems to work properly. Have a good weekend!

I'll see if we can get a new version built that includes an option to output the full log to the console after a job completes. In the meantime, you could call romp with a simple batch script like: romp install %1 romp jobs logs Then invoke it with: romp.bat <packageName> Let me know if that's helpful!

I also don't get why this is not implemented in upack. This prevents me from using it.

Thanks for the heads up, I fixed the docs and it should be live soon. Always happy to improve docs, so please let us know other issues you find, either here or even directly on the inedo-docs public repository.