This is the file we are currently using. Kindly provide an updated version of this file to help reduce the deployment footprint. My codebase includes both NestJS and VueJS; the attached file pertains to the VueJS project. I plan to use a similar approach for the NestJS deployment as well.

# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
# More GitHub Actions for Azure: https://github.com/Azure/actions
name: Build and deploy Node.js app to Azure Web App - name_xxx
on:
  push:
    branches:
      - deployment_internal
  workflow_dispatch:
jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
    steps:
      - uses: actions/checkout@v4
      - name: Set up Node.js version
        uses: actions/setup-node@v3
        with:
          node-version: '20.x'
      - name: npm install, build
        run: |
          npm install
          npm run build
      - name: Zip artifact for deployment
        run: zip release.zip ./* -r
      - name: Upload artifact for deployment job
        uses: actions/upload-artifact@v4
        with:
          name: node-app
          path: release.zip
  deploy:
    runs-on: ubuntu-latest
    needs: build
    environment:
      name: 'Production'
      url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}
    permissions:
      id-token: write
      contents: read
    steps:
      - name: Download artifact from build job
        uses: actions/download-artifact@v4
        with:
          name: node-app
      - name: Unzip artifact for deployment
        run: unzip release.zip
      - name: Login to Azure
        uses: azure/login@v2
        with:
          client-id: ${{ secrets.AZUREAPPSERVICE_CLIENTID_xxxx }}
          tenant-id: ${{ secrets.AZUREAPPSERVICE_TENANTID_xxxx }}
          subscription-id: ${{ secrets.AZUREAPPSERVICE_SUBSCRIPTIONID_xxxx }}
      - name: 'Deploy to Azure Web App'
        id: deploy-to-webapp
        uses: azure/webapps-deploy@v3
        with:
          app-name: 'xxxx'
          slot-name: 'Production'
          package: .

Hi Rashmi Panda,

Hoping that you are deploying to windows web app service , if not please let me know, slowness also depends on the size of artifact

The reason for slow deployment may also due to Kudu takes the ZIP it receives, then extracts it, and copies all files into /home/site/wwwroot.

To speed up the process, add the application setting WEBSITE_RUN_FEOM_PACKAGE=1 in the App Service=>Environment variables GitHub issue. This setting will deploy the app service to read only file system (read-only for wwwroot folder), This works only for Windows-based App Services

WEBSITE_RUN_FROM_PACKAGE=1 This setting tells Azure to run your app directly from the ZIP package, skipping the entire unzip-and-copy process.

You can set this in your GitHub Actions workflow mentioned above or directly in Azure:

- name: Set WEBSITE_RUN_FROM_PACKAGE
  run: |
    az webapp config appsettings set 
      --name 
      --resource-group <
      --settings WEBSITE_RUN_FROM_PACKAGE=1

Under configuration -> Application Settings of App Service through Portal also:

Please refer- https://learn.microsoft.com/en-us/azure/app-service/deploy-run-package#enable-running-from-packageIf you have any further assistant, do let me know.

I am currently using the Azure App Service (Web App) with a Linux-based plan. It appears that the current approach may not be compatible with my configuration. Could you please share a suitable solution that aligns with my Azure service plan?

I am currently using the Azure App Service (Web App) with a Linux-based plan. It appears that the current approach may not be compatible with my configuration. Could you please share a suitable solution that aligns with my Azure service plan?