APPNETOS is under active development This website and its documentation are being prepared for public launch. Content and features may change.
Select Theme
Loading

Application Aliases

One implementation. Multiple independent application identities.

Reuse an existing APPNETOS application as the implementation behind a separately configured alias. Keep a common codebase while controlling routing, data, security and background execution for each application identity.

What is an application alias?

An application alias has its own application identity and references an existing implementation through origin. APPNETOS can execute origin classes while resolving alias-specific configuration and supported custom overrides. This is not a complete copy of the origin and does not automatically create isolated databases or worker processes.

Why use aliases?

Reuse application code

Run an established implementation under another application identity without duplicating its entire source tree.

Configure independently

Define alias-specific hosts, contexts, platform configuration and security settings.

Control data boundaries

Provide dedicated documents, collections and class mappings when the alias needs isolated business data.

Alias and origin at a glance

Alias application: alias-appnetos-dns-control
    application = alias-appnetos-dns-control
    origin      = appnetos-dns-control
    custom      = custom/alias-appnetos-dns-control/

Origin application: appnetos-dns-control
    provides reusable PHP implementations

APPNETOS Core
    resolves application identity, contexts and class mapping

The alias and origin share implementation code where configured, but data, authentication, queues, installation resources and external integrations require explicit decisions.

The implementation workflow

Start with an existing, working origin application. Prepare the alias custom directory and platform configuration, then create any required data classes and class mappings. Configure installation resources, commands, OpenAPI and workers before validating the complete runtime behavior.

For architecture details, also see Application Isolation and Platform Configuration.

Designed for reuse without hidden coupling

Application aliases help build multiple specialized deployments from a common foundation. Correct isolation is a configuration and testing responsibility: verify every data entry point, command, API route and worker process rather than relying on the alias name alone.

One Core. Unlimited Business Software.

Next Steps

Concept & Architecture

Explore Concept & Architecture

Configuration & Setup

Explore Configuration & Setup

Platform Configuration

Explore Platform Configuration

Documents & Collections

Explore Documents & Collections

Class Mapping

Explore Class Mapping

Installation Data

Explore Installation Data

Custom Classes & Resources

Explore Custom Classes & Resources

Install & Reinstall

Explore Install & Reinstall

Commands & OpenAPI

Explore Commands & OpenAPI

Workers & Docker

Explore Workers & Docker

Verification & Troubleshooting

Explore Verification & Troubleshooting