You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don’t think this is fully resolved yet. We’re still working with a customer who is struggling to get the bundled npm registry online from the docker-compose stack.
The issue description says the commented Verdaccio config is missing most of the required settings, including the correct containers, Verdaccio config, and Forge config. That matches what we’re seeing in practice. 
In our case, simply uncommenting the npm registry service was not enough. We also had to manually create the expected directories and provide a base Verdaccio config file before the service would even start:
npm/conf npm/storage npm/conf/config.yaml
This is the config file we had to add:
`storage: /verdaccio/storage
Before adding that file, the container would not come up cleanly because /verdaccio/conf/config.yaml was missing.
Another area that still seems unclear is how the registry authentication is expected to be bootstrapped. The FlowFuse configuration allows defining admin credentials for the npm registry, but in practice it wasn’t obvious how those credentials translate into a usable Verdaccio user during deployment.
At the moment it appears that some form of runtime bootstrap is still required (for example creating the first user or populating the htpasswd store), and this process does not seem to be fully driven by environment variables. We’re still working through this part with the customer and haven’t yet found a clearly documented path for initializing the registry credentials in an automated deployment.
From a deployment perspective this means there are still a few gaps:
1. The required Verdaccio directories and configuration file are not documented.
2. The registry container will not start without a valid config.yaml.
3. The expected process for bootstrapping registry credentials is still unclear and appears not to be fully env-driven.
Because of this, the customer we are working with is still struggling to get the npm registry online following the documented setup steps.
If someone from the FlowFuse team could help clarify the intended setup and bootstrap process for the bundled npm registry (especially around credential initialization in the docker-compose deployment), that would really help us unblock this deployment.
Ideally it would also be helpful to connect directly with the customer to work through this together, as they are currently blocked trying to get the registry online.
@dgatti0213 You MUST to pull the NEW docker-compose.yml, the old commented out section if NOT useful, it is using the wrong container and has none of the required configuration.
The latest docker-compose.yml file has all the required configuration and you don't need to create any directories as it uses docker volumes and the authentication is all handled by a custom authentication plugin via the forge app.
Activity
Add Team NPM registry support
dgatti0213 commentedon Mar 10, 2026
I don’t think this is fully resolved yet. We’re still working with a customer who is struggling to get the bundled npm registry online from the docker-compose stack.
The issue description says the commented Verdaccio config is missing most of the required settings, including the correct containers, Verdaccio config, and Forge config. That matches what we’re seeing in practice. 
In our case, simply uncommenting the npm registry service was not enough. We also had to manually create the expected directories and provide a base Verdaccio config file before the service would even start:
npm/conf npm/storage npm/conf/config.yamlThis is the config file we had to add:
`storage: /verdaccio/storage
auth:
htpasswd:
file: /verdaccio/storage/htpasswd
max_users: 1000
uplinks:
npmjs:
url: https://registry.npmjs.org/
packages:
"@/":
access: $all
publish: $authenticated
proxy: npmjs
"**":
access: $all
publish: $authenticated
proxy: npmjs
server:
keepAliveTimeout: 60
log:
Before adding that file, the container would not come up cleanly because /verdaccio/conf/config.yaml was missing.
Another area that still seems unclear is how the registry authentication is expected to be bootstrapped. The FlowFuse configuration allows defining admin credentials for the npm registry, but in practice it wasn’t obvious how those credentials translate into a usable Verdaccio user during deployment.
At the moment it appears that some form of runtime bootstrap is still required (for example creating the first user or populating the htpasswd store), and this process does not seem to be fully driven by environment variables. We’re still working through this part with the customer and haven’t yet found a clearly documented path for initializing the registry credentials in an automated deployment.
From a deployment perspective this means there are still a few gaps:
1. The required Verdaccio directories and configuration file are not documented.
2. The registry container will not start without a valid config.yaml.
3. The expected process for bootstrapping registry credentials is still unclear and appears not to be fully env-driven.
Because of this, the customer we are working with is still struggling to get the npm registry online following the documented setup steps.
If someone from the FlowFuse team could help clarify the intended setup and bootstrap process for the bundled npm registry (especially around credential initialization in the docker-compose deployment), that would really help us unblock this deployment.
Ideally it would also be helpful to connect directly with the customer to work through this together, as they are currently blocked trying to get the registry online.
https://app-eu1.hubspot.com/contacts/26586079/record/0-1/334502
hardillb commentedon Mar 10, 2026
@dgatti0213 You MUST to pull the NEW docker-compose.yml, the old commented out section if NOT useful, it is using the wrong container and has none of the required configuration.
The latest docker-compose.yml file has all the required configuration and you don't need to create any directories as it uses docker volumes and the authentication is all handled by a custom authentication plugin via the forge app.
dgatti0213 commentedon Mar 11, 2026
I think he is experiencing the Quick-Start -> Full Docker Compose file scenario...
dgatti0213 commentedon Mar 11, 2026
I need help on this. I do not have any open slots in my calendar tomorrow to help.
@robmarcer @hardillb Can one of you please help him?
Add Team NPM registry support (FlowFuse#291)