flb set-auth

Write a registry auth token into your Fleetbase instance's console/.npmrc (for npm) and api/auth.json (for Composer). Run this after flb verify or flb generate-token returns a token.

flb set-auth <token>

The token is the value printed by verify or generate-token. The CLI writes it for both package managers in one shot — Fleetbase extensions are typically dual-distributed (npm package for the addon, Composer package for the API), and both auth files need the token.

Options

Examples

From inside your Fleetbase directory

cd /path/to/fleetbase
flb set-auth <token>

From anywhere with --path

flb set-auth <token> --path /path/to/fleetbase

Self-hosted registry

flb set-auth <token> --registry https://registry.mycompany.com

What Gets Written

flb set-auth updates two files inside your Fleetbase instance:

If console/.npmrc already exists, the token line is appended — existing auth lines for other registries are preserved. The same applies to api/auth.json — existing bearer entries for other hosts are kept and the new entry merged in.

Path Resolution

The CLI resolves the Fleetbase instance path in this order:

1. The path passed via --path, or the current directory
2. If neither contains both console/ and api/ subdirectories, falls back to /fleetbase

If neither location is a valid Fleetbase install, set-auth writes anyway — but the resulting files won't be picked up by your installer until you copy them into the right place.

When You Need This

You need to set auth on the instance whenever you're going to:

• Install a paid or private extension — flb install needs _authToken access to fetch the package from the registry
• Develop against a registry — composer require and pnpm install from your console / api need credentials

You do not need flb set-auth to install public free extensions.

Difference from flb login