@apxltd I understand what you mean

When I have your attention I would like to just tell you that you have done an amazing work on ProGet as a product. It has everything we need while not being overcomplicated or overpriced. It really is a great product.

And the support through this forum is also always superb, fast and accurate.

Great work!

@apxltd I see, thanks for the info!

The use cases seems legit I think, like bundling multiple packages. Why would you like to have it undone?

I stumbled upon this V symbol when scrolling through Inedos open feeds. What does it mean and how does one add it? :)

@dean-houston

Ahh, thanks for pointing that out :)

As an answer to my question about health (and for anyone coming here in the future), I should've just read the docs properly, it was very clear what to check I love Proget! These things just exists and are well documented 🥰

https://docs.inedo.com/docs/proget-reference-api-health

Hi there!

We run Proget as an Azure Container Web App atm with great success. To this we have an Azure SQL DB and we have mounted an Azure storage account file share at /var/proget to get all the files stored in Azure and backed up there. Everything deployed with Bicep, which is awsome

There are some cool features for Azure Web Apps though that I would like to utilize to maximize the robustness and up time of our Proget instance for our developers.

One such feature is the "scale out" together with "Health check". This (if I understand correctly) would allow me to run multiple instances of the Proget container and Azure will ping them to see if they are healthy. If one is deemed unhealthy it will be brought down and replaced.

I however have some concerns about what happens if I scale out the web app to multiple instances but they all have the same SQL database and file share? The file share shouldn't be an issue, but what about the database? Can it handle writing and reading from multiple instances of an Azure Container Web App? Do you have any experience or best practices regarding this? I'm not very experienced with DB:s, and my biggest concern is that there will be any deadlock, corrupt data and overall breakage of the data in the DB, but maybe that is not a concern.

Also when on the topic, do you have any recommended path to probe/ping for checking health of both the Proget instance and the SQL DB connection?

I guess some endpoint which tries to read something from the DB and returns a non 200-299 code if the read fails would be good. It should be something "static" and not a path to a package which could be removed any time in the future.

(If there are concerns with the DB I guess a single instance with "auto replace" by the health check is good enough, but this would cause a one hour downtime which would be nice to not have )

It should be noted that we do not have any kind of load on Proget since we are pretty few devs, I would only like to use these features to increase the uptime and robustness of the app since people will come and complain at me if Proget is down

Cheers
Carl

@atripp, I can confirm that 2024.1 works great

Awsome @atripp, thanks for the quick support!

@atripp

Yep, it's there

schema_id = 4
is_ms_shipped = True

I'm no database master of any kind, but I think I've chosen all defaults when creating both the Az sql server and the db

Hi @atripp,

When creating a new empty Azure SQL DB this seems to be there by default.

It's also present in my Proget DB