Verification & Troubleshooting
Validate isolation, runtime behavior and diagnose common alias mistakes.
Identity and routing
Verify alias configuration filenames, `application` and `origin`, environment selection, hosts, slugs and contexts. Confirm that the origin remains independently reachable.
Data and access isolation
Verify all concrete collection/document pairs, class mappings, seed/index names, authentication and Core Apps. Test that alias users cannot accidentally authenticate against origin data.
Runtime integrations
Verify templates, REST/OpenAPI server URLs, security, CORS, command names, worker queues, scheduler/runner processes, uploads, external services and deployment targets. Investigate each integration separately rather than assuming one successful page request validates the alias.
Configuration and command examples
These examples are preserved from the alias pre-documentation. Review the active environment and application names before applying them.
rg -n -A 18 "'cmd'" platform/autoload/alias-appnetos-dns-control*.php
rg -n "'application'|'origin'" platform/application/alias-appnetos-dns-control*.php
rg -n "'key'|'queue'|'class'" custom/alias-appnetos-dns-control/.files/Worker/workers.php
ls -l appnetos-dns-control/worker/src/AppnetosDnsControl/Worker/DeployConfiguration.php