---
# System prepended metadata

title: Deployments and NPM Pairing (6/29/22)
tags: [' blacksmiths', ' deployment', v3]

---

---
tags: v3, blacksmiths, deployment
---

# Deployments and NPM Pairing (6/29/22)

## npm Publish

- `nx-web3-plugins`
    - version is managed through the package.json
    - name, dependencies
    - To specificy, we use `ngx-deploy-npm:deploy` and we tag as public and alpha
    - would need to explicitly set someone is using it since we tag it as alpha
    - can't push the same version multiple times
    - any time we modify a package we'll have to bump the version
    - can add a check in the CI for this for non-prod builds
    - would it bump on main or develop? - we don't want to deploy on develop, only on merges into master
    - would this only happen on branches that have a PR open on master?
    - merging into develop we won't get a build failure since we're not publishing anything but if we publish into master we'll then need to be sure to bump our versions
    - we have the `daohaus` username on`npm`
    - What happens if we change package names?
    - Change in the `nx` path and then it'll publish to a different
    - Could likely go in and deprecate after changing the name
    - Going forward we should add to the individual package.json in each library's package
    - add a `generatePackageJson` in the `build` step in the package's `package.json`
    - look into how to automatically bump the versions via nx or GitHub Actions
    -  

## SSL

- For SSL, we'd need to generate our own certificates using something like Let's Encrypt
- Skynet doesn't issue SSL certs but would need a DNS layer to take care of the support such as with Cloudflare
- Netlify -> Cloudflare -> Skynet



