Run BaGet on Azure¶
Warning
This page is a work in progress!
Use Azure to scale BaGet. You can store metadata on Azure SQL Database, upload packages to Azure Blob Storage, and provide powerful search using Azure Search.
TODO¶
- App Service
- Table Storage
- High availability setup
Configure BaGet¶
You can modify BaGet's configurations by editing the appsettings.json
file. For the full list of configurations, please refer to BaGet's configuration guide.
Azure SQL database¶
Update the appsettings.json
file:
{ ... "Database": { "Type": "SqlServer", "ConnectionString": "..." }, ... }
Azure Blob Storage¶
Update the appsettings.json
file:
{ ... "Storage": { "Type": "AzureBlobStorage", "AccountName": "my-account", "AccessKey": "abcd1234", "Container": "my-container" }, ... }
Alternatively, you can use a full Azure Storage connection string:
{ ... "Storage": { "Type": "AzureBlobStorage", "ConnectionString": "AccountName=my-account;AccountKey=abcd1234;...", "Container": "my-container" }, ... }
Azure Search¶
Update the appsettings.json
file:
{ ... "Search": { "Type": "Azure", "AccountName": "my-account", "ApiKey": "ABCD1234" }, ... }
Publish packages¶
Publish your first package with:
dotnet nuget push -s http://localhost:5000/v3/index.json package.1.0.0.nupkg
Publish your first symbol package with:
dotnet nuget push -s http://localhost:5000/v3/index.json symbol.package.1.0.0.snupkg
Warning
You should secure your server by requiring an API Key to publish packages. For more information, please refer to the Require an API Key guide.
Restore packages¶
You can restore packages by using the following package source:
http://localhost:5000/v3/index.json
Some helpful guides:
Symbol server¶
You can load symbols by using the following symbol location:
http://localhost:5000/api/download/symbols
For Visual Studio, please refer to the Configure Debugging guide.