Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
[ProGet] Currently recommended setup for Azure Deployment using Windows Server VM
-
Moin!
I was wondering what your current recommendations for an Azure Setup of ProGet using a Windows Server VM are.
I already read the following article:
https://docs.inedo.com/docs/proget/installation/proget-migrate-instance-to-azureThe article recommends "Azure SQL" for the database. Is this still your recommendation for the Azure Setup? If so, what is your reasoning behind it, concerning
- In the Azure Setup I already did (we are currently in testing of it), it was quite complicated to use a stand-alone database instead of the included InedoDB that also runs on the VM
- Azure SQL / MSSQL is only supported through "at least ProGet 2026"
- The main "data" portion of ProGet is not stored in the database, but on disk anyways, so separate data storage is not as useful as it might be for other applications that are only relying on the database
I am probably missing some arguments for why the recommended setup makes sense ^^
But since I am currently still in the set-up of our new ProGet instance, I would like to clear out these questions before proceeding. -
Hi @jonathan-werder_8656,
Oooh that's definitely outdated, thanks for pointing that out! Perhaps we should just delete that article.... but I'll see if we can salvage it.
If you're setting up a new instance of ProGet, that article is not for you -- that's helping you migrate an existing instance. For a new instance, I would just do a standard Windows or Linux installation (use the Embedded database in either case) - there's nothing special about Azure.
For migrating... at this point (i.e. ProGet 2025+), I would just set-up ProGet on the new server using PostgreSQL (the default configuration). Then, export your database from the old server and import it into the new server.
You'll have to deal with the Package Files as well, which is discussed in this (slightly outdated) Migrate an Existing ProGet Installation to a New Server article.
Anyway we'll add these to the list, but let me know if you have any questions in the meantime.
Cheers,
Alana -
@atripp
Moin and thanks for the quick response!I used that article as there weren't and comparable recommendations for an Azure set-up of ProGet in the documentation and the "Azure-Migration" set-up was different from the regular installation set-up, that's why I assumed that a separate database was recommended for cloud installations.
Perhaps you should write a separate "Azure" article (that is not about the migration) to specify recommendations or write Azure recommendations into the regular install guide, I think.
-
Hi @jonathan-werder_8656 ,
We actually don't have any Azure-specific recommendations (or Amazon, GCP, or any host really) -- so just the normal Windows or Linux (Docker) guidance would apply.
Happy to clarify that in the docs if you can think of a good pace to put that :)
Thanks,
Alana
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login