Skip to content

Fix $ escaping and add LETSENCRYPT for npm registry#296

Merged
ppawlowski merged 1 commit intomainfrom
escape-verdaccio-auth
Mar 11, 2026
Merged

Fix $ escaping and add LETSENCRYPT for npm registry#296
ppawlowski merged 1 commit intomainfrom
escape-verdaccio-auth

Conversation

@hardillb
Copy link
Contributor

fixes #295

Description

  • Add the missing env var to the npm-registry service
  • double up the $ in the npm-registry config to prevent it being subsituted

Related Issue(s)

#295

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

@hardillb hardillb self-assigned this Mar 11, 2026
@ppawlowski ppawlowski merged commit f40c64c into main Mar 11, 2026
3 checks passed
@ppawlowski ppawlowski deleted the escape-verdaccio-auth branch March 11, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enabling the FlowFuse NPM Registry with Docker, nginx-proxy, and Let’s Encrypt

2 participants