Skip to main content

Azure Static Web Apps – VS Code extension

As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.

In this first post I’ll focus on the Azure Static Web apps extension for VS Code. After installing this extension you can quickly create your Static Web App directly from the VS Code IDE.

  • Open a folder that contains your frontend app in VS Code.
  • Go to the Azure Extension and click on the ‘+’ sign.
  • Choose Create Static Web App from the list of options.
  • Specify a name for the new SWA.
  • Select a region for your staging environments and the Managed Azure Function(if you have one).
  • Now we can choose a preset to configure the default project structure. Azure Static Web Apps will use this information to determine things like the location of our code, build location, etc…
    • In our example we have created a static web site using Astro, a static site generator. As no preset exists for Astro we need to select the Custom option.
  • Now we get some last questions. First we need to specify the location of our application code. We can leave this to the default(the current folder).
  • As a last step we need to specify the location of our build output. For Astro this is the ‘dist’ folder.
  • The Azure extension will create our Azure Static Web App.
  • Also a Github actions workflow is created and this workflow is pushed to Github. After this is done the workflow is executed to deploy our new web app.

Once the workflow completes we can browse to our newly created Static Web App.

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more