メニュー
Manage a local Business Central instance for development and testing. Detects host vs container environment automatically. Uses bc-linux run-tests.sh for test execution.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | local-bc |
| description | Manage a local Business Central instance for development and testing. Detects host vs container environment automatically. Uses bc-linux run-tests.sh for test execution. |
A local BC instance for compiling, publishing, and running tests.
Check $BC_SERVER to determine how to reach BC:
| Environment | $BC_SERVER | BC address |
|---|---|---|
| Host (direct) | unset | localhost |
| Sandboxed container | set (e.g. 172.17.0.1) | $BC_SERVER |
Inside a container: You cannot start or stop BC — there is no Docker CLI or socket. The user must start the BC stack on the host before you can use it. If BC is not reachable, tell the user:
BC is not running. Please start it on the host:
cd ~/Documents/Repos/community/bc-linux && docker compose up -d --wait
BC_HOST="${BC_SERVER:-localhost}"
curl -sf -u BCRUNNER:Admin123! "http://${BC_HOST}:7049/BC/dev/metadata" > /dev/null 2>&1 \
&& echo "BC is running" || echo "BC is NOT running"
| Service | URL | Auth |
|---|---|---|
| Dev (publish/symbols) | http://${BC_HOST}:7049/BC/dev | BCRUNNER:Admin123! |
| OData | http://${BC_HOST}:7048/BC/ODataV4 | BCRUNNER:Admin123! |
| API | http://${BC_HOST}:7052/BC/api | BCRUNNER:Admin123! |
| Web Client / WebSocket | http://${BC_HOST}:7085 | BCRUNNER:Admin123! |
bc-publish # Uses .bcconfig.json or $BC_SERVER automatically
Or with curl:
BC_HOST="${BC_SERVER:-localhost}"
curl -u BCRUNNER:Admin123! -X POST \
-F "file=@path/to/app.app;type=application/octet-stream" \
"http://${BC_HOST}:7049/BC/dev/apps?SchemaUpdateMode=forcesync"
Publish dependencies first, then the main app, then the test app.
Tests use the run-tests.sh script from the bc-linux repo, mounted at /opt/bc-linux.
BC_HOST="${BC_SERVER:-localhost}"
/opt/bc-linux/scripts/run-tests.sh \
--base-url "http://${BC_HOST}:7048/BC" \
--dev-url "http://${BC_HOST}:7049/BC/dev" \
--app path/to/test-app.app
Options:
--app <path> — Test .app file (auto-published + codeunit IDs auto-discovered)--codeunit-range <range> — Codeunit ID range (e.g. 70000 or 70000..70001)--base-url <url> — BC OData base (default: http://localhost:7048/BC)--dev-url <url> — BC Dev endpoint (default: http://localhost:7049/BC/dev)--auth <user:pass> — Credentials (default: BCRUNNER:Admin123!)--timeout <minutes> — Overall timeout (default: 30)What the script does:
--app given)If /opt/bc-linux is not mounted, tell the user to add this volume to their
docker run command:
-v "$HOME/Documents/Repos/community/bc-linux:/opt/bc-linux:ro"
BC_HOST="${BC_SERVER:-localhost}"
mkdir -p .alpackages
for app in "System" "System Application" "Base Application" "Application"; do
curl -sf -u BCRUNNER:Admin123! \
"http://${BC_HOST}:7049/BC/dev/packages?publisher=Microsoft&appName=$(echo $app | sed 's/ /%20/g')&appVersion=0.0.0.0" \
-o ".alpackages/${app}.app" && echo "Downloaded ${app}" || echo "Failed: ${app}"
done
Both bc-publish and bc-test auto-detect $BC_SERVER when no .bcconfig.json
exists. If a .bcconfig.json is present, its server field takes precedence.
{
"server": "http://localhost",
"port": 7048,
"instance": "BC",
"authentication": "UserPassword",
"username": "admin",
"password": "Admin123!"
}
Inside a container, either omit .bcconfig.json (tools use $BC_SERVER
automatically) or set "server" to "http://<BC_SERVER value>".
.alpackages/al-compile)bc-publish or curl)/opt/bc-linux/scripts/run-tests.sh --app <test.app> --base-url ...)The user runs this (you cannot run it from inside a container):
cd ~/Documents/Repos/community/bc-linux && docker compose up -d --wait
First boot takes 5-10 minutes (artifact download + DB restore). Subsequent starts ~20 seconds.
To set a specific version:
BC_VERSION=27.5 BC_COUNTRY=w1 docker compose up -d --wait
To stop:
docker compose down # Keep data
docker compose down -v # Full reset
Run mutation testing against an AL project using al-mutate (MSDyn365BC.AL.Mutate). Identifies test gaps by applying AST-based mutations and checking whether the test suite catches them via al-runner. No BC instance required. Produces mutations.json and report.md.
Download AL symbol packages (.app files) for the current project's dependencies from Microsoft NuGet feeds. Reads app.json to determine required packages.
Look up Business Central base application source code (tables, pages, codeunits, events) from MSDyn365BC.Sandbox.Code.History. Use this to verify object structures, find event publishers, or check field definitions.
Quick reference for AL build pipeline. Auto-load when compilation, deployment, or testing is mentioned. For running commands, use /compile, /publish, or /run-tests.
Compile the AL project using al-compile. Runs analyzers, reports errors, and writes diagnostics to the task folder.
Implement AL/BC solution using parallel development agents and 4-specialist review team. Spawns N developer agents for parallel modules, then 4 reviewer agents for comprehensive code review.