Topics created by james.woods_8996

Hi @james-woods_8996 , I looked into this a little more, and it turns out that our cloud storage providers do in fact support chunking -- but the outgoing replication code is not taking advantage of that. We would like to fix that in ProGet 2026. However, in the meantime, we can fix the incoming replication code (i.e. what's throwing the error) pretty easily via PG-3102 - hopefully we'll get that in the upcoming maintenance release. Thanks, Alana

Thanks for that, I'd put an alphanumeric rather than a hex key in two of my sites. Once I changed them to hex then all started working.

Thanks for that, we enabled the multipart header but then encountered another error. We've raised a ticket with the vendor.

@james-woods_8996 good to know - I've just removed that from the docs since I think that was an instruction from earlier versions (before ProGet 2022 maybe)

Hi @james-woods_8996 , No problem using ProGet 2025 Docker Image with SQL Server - it works exactly as it did in ProGet 2024. We will continue to support SQL Server in the through at least ProGet 2026. Thanks, Steve

Hi @james-woods_8996 , You are correct - in a mirror scenario, either side could publish (or delete) packages, and it would be propagated to the other. Three-way is also possible, but you do that with two two-way relationships, if that makes sense? So it's basically A <--> B + B <--> C, and that means if you publish/delete a version on A it will propagate like A --> B --> C. Thanks, Steve

Thanks Dean, that makes it clear for me.