SettingUpDemosInAzure
azure-quickstart-templates
SettingUpDemosInAzure | azure-quickstart-templates | |
---|---|---|
2 | 42 | |
0 | 13,724 | |
- | 0.5% | |
2.6 | 9.9 | |
about 3 years ago | 6 days ago | |
C# | Bicep | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SettingUpDemosInAzure
-
Setting up demos in Azure - Part 2: GitHub Actions
The source code for this post is in the SettingUpDemosInAzure repository.
-
Setting up demos in Azure - Part 1: ARM templates
Right out of the gate, even if this section is called "sample template", I won't put it all here, as it's a big JSON file which won't be readable on the blog. I'll drop a couple of bits here, but to see the whole thing, better head to GitHub.
azure-quickstart-templates
- Instantly Deploy BrowserBox on Azure Cloud – open-source isolated browser
- Deploy BrowserBox from an Azure Quickstart Template
- Chef extension for Azure VM
-
Chef extension for Azure VM in Bicep
I found a quick start template for this in Arm, I’m sure if you just decompile the ARM json it will give you a good heads start on how it should work.
-
Bicep: Cyclical Dependency Issue (Network resources)
There is a GitHub issue regarding this topic - https://github.com/Azure/azure-quickstart-templates/issues/2786
- Struggling to understand "_artifactsLocation" parameter when using ARM templates
-
Removing secondary disk
I'm using this video (https://www.youtube.com/watch?v=J4NCvIMuzVE) as a guide to start building out Windows VM's, and running into some questions. I'm trying to use the template located here ( azure-quickstart-templates/quickstarts/microsoft.compute/vm-simple-windows at master · Azure/azure-quickstart-templates (github.com)).
- The yaml document from hell
-
ARM / Bicep template development just by hand?
You can use quick start templates (https://github.com/Azure/azure-quickstart-templates/) as a starting point, but not all examples are bicep ready yet. But those can be easily converted to bicep.
-
SFTP for Azure Blob Storage Generally Available - Pricing
I think it was this one https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files-existing-storage and this https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files
What are some alternatives?
azure-cli-extensions - Public Repository for Extensions of Azure CLI.
bicep - Bicep is a declarative language for describing and deploying Azure resources
photoprism-auto-index - Photoprism supercharged with originals folder auto indexing
Enterprise-Scale - The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
protonmail-bridge-docker - ProtonMail IMAP/SMTP Bridge Docker container
opnazure - This template allows you to deploy an OPNsense Firewall Azure VM using the opnsense-bootsrtap installation method
Moodle - Tooling and guidance on deploying Scalable Moodle Clusters on Azure.
ffmpeg-on-apple-silicon - Build ffmpeg for ARM-based Apple Silicon Macs
aws-cdk-examples - Example projects using the AWS CDK
azure-policy - Repository for Azure Resource Policy built-in definitions and samples