npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@azbake/ingredient-host-names

v0.1.115

Published

Ingredient for deploying custom host names and ssl certs to an Azure WebApp

Downloads

163

Readme

Changelogs

Overview

The host names ingredient is a plugin for bake. When included in a recipe, this plugin will install vanity host names for your web app, and secure it with a certificate of your choice from your app svc plan.

Before deploying a custom host name with ssl binding, be sure that your custom domain has been configured to route traffic to the azure website.

This ingredient assumes that you already have a key vault configured with your ssl cert uploaded and associated to the app service plan.

Please note when setting up your keyvault and app svc plan, that the "Microsoft Azure App Service" must have "Get" permissions for secrets in the keyvault in order for the deployment to read and use the certificate. You can accomplish this with the following powershell, or the portal:

Set-AzureRMKeyVaultAccessPolicy -VaultName myenvkvtest -ServicePrincipalName abfa0a7c-a6b6-4736-8310-5855508787cd -PermissionsToSecrets get

Note that the serviceprincipal name / id in the above statement is global across all of Azure.

Usage

Recipe

name: My package
shortName: mypkg
version: 0.0.1
ingredients:
  - "@azbake/ingredient-host-names@~0"
resourceGroup: true
recipe:
  mypkg-ssl:
    properties:
      type: "@azbake/ingredient-host-names"
      source: "mysite.mydomain.com"
      parameters:
        certificate: "certificate_resourceGroup/certificate_name"

|property|required|description| |---------|--------|-----------| |source|yes|The url of custom domain being added| |certificate|yes|The name of the ssl certificate to use in key vault. Format <resourceGroup>/<resource> ***|

*** Please note that you can supply just the name of the azure resource for the source if the resource exists within the same resource group that is currently being deployed for traffic manager.

*** Please note that all values should be in the parameters section of the recipe except for source