RRonald A. Richardsonci(api-contract): run the QPay callbacks after the checkout that creates their id

e32a5246创建于 8月14日历史提交

文件	最后提交记录	最后更新时间
ci	ci(api-contract): run the QPay callbacks after the checkout that creates their id Both QPay callbacks address {{checkout_id}}, and Checkout/Before is the only request that sets it. In folder order they sort ahead of Before, so they were sent the literal string "{{checkout_id}}" and answered CHECKOUT_SESSION_NOT_FOUND on every run — a failure manufactured entirely by ordering. Moving them to the tail of RUN_LATE puts them after Before, Capture and Get Checkout Status, so they address a real checkout. What this covers, precisely: capture-qpay short-circuits to a synthesised result when the checkout's gateway is in sandbox and `test` is success\|error. It checks the sandbox FLAG, not the gateway type, and the seeded storefront gateway is sandbox — so this exercises the documented test-scenario branch and nothing more. The real invoice-check path needs live QPay credentials and cannot run in CI; that remains uncovered and is stated in the comment rather than implied to be green. Emitted order is byte-identical for Fleetbase API, Core API, Ledger API and the Integrated Vendor Flow; only the two Storefront entries move. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	1 个月前
README.md	fix package-linker script	4 个月前
docker-install.sh	fix(install): non-interactive installs could not send mail at all scripts/docker-install.sh writes its values into docker-compose.override.yml via env_line(), which SKIPS empty values. MAIL_FROM_ADDRESS defaulted to "", so the key never reached the container environment — and api/.env.example ships the literal string MAIL_FROM_ADDRESS=null which OVERRIDES config/mail.php's default rather than falling back to it. Every non-interactive install therefore ran with an unusable from-address: Email "null" does not comply with addr-spec of RFC 2822. That is a 400 on every verification-code endpoint and a 500 on any notification send — password resets, login codes, work orders. It affects self-hosted installs, not just CI. The default now matches config/mail.php's own, so the result is the same as if the key were genuinely unset. Also moves the contract workflow's mail block to BEFORE the installer. The earlier placement after it did not take: Laravel parses .env once at boot, and config:clear plus octane:reload both ran while the endpoints kept answering Email "null", because the workers were already holding the parsed values. Verified against a real run — the step logged "Mail transport: log" and the five affected requests failed unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	1 个月前
package-linker.mjs	fix security alerts from package-linker script	4 个月前
package-linker.test.mjs	fix package-linker script	4 个月前
package-lock.json	fix package-linker script	4 个月前
package.json	fix package-linker script	4 个月前

Fleetbase Scripts

This directory contains project-level utilities for local development and setup. Run all commands from the repository root unless a command says otherwise.

`package-linker.mjs`

flb-package-linker manages local Fleetbase package links for extension development. It updates the Console npm manifest, API Composer repositories, and Console pnpm workspace settings so linked extension packages and shared Ember packages resolve from packages/*.

Use this when working on an extension such as FleetOps and you need local changes from packages/fleetops, packages/ember-ui, packages/ember-core, or packages/fleetops-data to show up in the host app.

The linker only treats a package as a Fleetbase extension when either:

its package.json has fleetbase-extension in keywords
it has an extension.json manifest

The only non-extension packages supported for shared dependency linking are @fleetbase/ember-core, @fleetbase/ember-ui, @fleetbase/fleetops-data, and the backend-only fleetbase/core-api.

Install as a Global CLI

From the repository root:

npm link

Or from this directory:

cd scripts
npm link

After that, use:

flb-package-linker --help
flb-package-linker status

Without global linking, run the script directly:

node scripts/package-linker.mjs status

Common Commands

List packages discovered under packages/*:

flb-package-linker list

Show currently linked packages and shared dependency resolution:

flb-package-linker status

Check for missing local symlinks or duplicate Fleetbase package versions in console/pnpm-lock.yaml:

flb-package-linker doctor

Preview FleetOps linking without changing files:

flb-package-linker enable fleetops --shared ember-core ember-ui fleetops-data --dry-run

Enable FleetOps local development links:

flb-package-linker enable fleetops --shared ember-core ember-ui fleetops-data
flb-package-linker install

Enable multiple extensions at once:

flb-package-linker enable fleetops pallet --shared ember-core ember-ui fleetops-data
flb-package-linker install

Run the install/update step for specific extensions:

flb-package-linker install fleetops pallet

Preview the install/update commands without running them:

flb-package-linker install --dry-run

Reset all local development links managed by the linker:

flb-package-linker reset
flb-package-linker install

Preview a full reset without changing files:

flb-package-linker reset --dry-run

Enable only a shared frontend package:

flb-package-linker enable-shared ember-ui
flb-package-linker install

Enable the backend-only Core API package:

flb-package-linker enable-shared core-api
flb-package-linker install core-api

Disable local links and restore saved registry ranges:

flb-package-linker disable fleetops pallet
flb-package-linker disable-shared ember-core ember-ui fleetops-data core-api
flb-package-linker install fleetops pallet core-api

Run installs automatically after enabling:

flb-package-linker enable fleetops --shared ember-core ember-ui fleetops-data --install

What It Changes

Depending on the command, flb-package-linker may update:

console/package.json
console/pnpm-workspace.yaml
console/.npmrc
api/composer.json
.fleetbase-dev-links.json

The .fleetbase-dev-links.json file stores original dependency ranges so links can be reversed. It is ignored by git.

For pnpm, the linker moves non-auth public-hoist-pattern[] settings from console/.npmrc into console/pnpm-workspace.yaml, keeps registry auth in .npmrc, and sets workspace linking options for local shared packages.

`docker-install.sh`

docker-install.sh is the interactive Fleetbase Docker setup wizard. It checks required local tools, asks for core environment settings, generates local configuration, and guides Docker Compose setup.

Run the interactive wizard:

bash scripts/docker-install.sh

Run with defaults for non-interactive environments:

bash scripts/docker-install.sh --non-interactive

The script expects Docker, Docker Compose v2, git, and OpenSSL to be available. It warns when common Fleetbase ports are already in use but does not treat that as a hard failure.

Validation

Check the package linker script:

node --check scripts/package-linker.mjs
node --test scripts/package-linker.test.mjs

Check shell syntax for the Docker installer:

bash -n scripts/docker-install.sh