@stijn-peeters-external_8202 Thanks for letting us know; we do have plans to improve this in ProGet 2023, and make it much easier to use.

@jim-borden_4965 glad you got it working :) On Windows, you can just do an in-place upgrade of MSSQL, and not worry about database migrations. The same is probably true on Docker, and you can just upgrade container. Anyways safer to back-up. And if you haven't seen it already, here is the ProGet guidance: https://docs.inedo.com/docs/installation-backing-up-restoring

Hi @andrewwickham_1641, Thanks for giving us an update and letting us know that fixed your issue. Thanks, Rich

Hi @torgabor_4445 and @sdohle_3924, I dug deeper into GitLab connectors and it looks like there are two ProGet issues here and a configuration issue. PG-2210: GitLab does not return the "time" property when it returns package metadata. This causes ProGet to fail to return any packages. PG-2211: There is a display issue when entering only a password with bearer authentication. The UI will show anonymous, even though it will use the token. Configuration Issue: here is what you will need to configure a GitLab connector. Connector URL: https://gitlab.com/api/v4/projects/12345/packages/npm/ User Name: leave blank Password: Generate a personal access token with API access and set that value there. Authentication: Bearer Advanced Options: Check exact package match only. GitLab does not support partial searching and/or listing I have added fixes for PG-2210 and PG-2211 and they will release tomorrow in ProGet 2022.9. Once you upgrade to 2022.9 and make the configuration updates, you should be able to pull GitLab packages via a connector. Thanks, Rich

Hi @itinfrastructure_7135 , The easiest approach is this: Notify users of downtime Shutdown old server Migrate database, files Start the new server Edit DNS to the new server Using the drop-path isn't required, and that whole process probably wouldn't take too long. There are ways to reduce downtime, but that mostly involves using something like "robocopy" or another tool to mirror the package files across servers. The database is relatively small to backup/restore. Otherwise it sounds like you're on the right track! Cheers, Alana

OK, by selecting the correct version, I managed to upgrade manually the extensions. Many thanks for your time, Marc

Thank you. I will do that.

Oh, if you meant an example with embedded icon, .NET official packages do this too: https://www.nuget.org/packages/System.Collections.Immutable/7.0.0-rc.1.22426.10

Created repo including working docker-compose file + some guide. https://github.com/Relers/proget-nginx

Fantastic, that worked and I learned something new today :) "Regional settings are per user" and since ProGet runs under Network Services account, changing it simply for the current user made no difference. Awesome support, thank you! K>

Thank you very much for the support! Have a nice week. Regards!

we have tried both the ways [image: 1662524666807-2c8eb346-0435-4786-96f3-e075f4001f4c-image.png]

@gdivis

Hi @proget_3280, Can you please tell me what version of ProGet you are using? Thanks, Dan

@gdivis That was it - I had to override PROGET_SQL_CONNECTION_STRING. I had to override it as: environment: - "PROGET_SQL_CONNECTION_STRING= " # would fail: #- PROGET_SQL_CONNECTION_STRING= - PROGET_SQL_CONNECTION_STRING_FILE=/run/secrets/mssql-cs Else startup would fail with "System.ArgumentNullException: Value cannot be null. (Parameter 'connectionString')" In any case, I have a working docker compose file now - thanks!

@Dan_Woolf Sounds good, thanks for the response.

Good news! Thanks!