StackX conventions keep the roles, environments, and machines operated by ScalarX easy to identify.
They do not replace a server’s actual name: the hostcode can be generated automatically or selected with the client when the fleet, contract, or operating procedures warrant it. StackX also relies on controlled installation templates; for clients with a sufficiently large fleet, a dedicated template can be designed when it provides real operational value.
The suffix indicates the operational role. This convention simplifies communication, bastion inventory, PRD / DRS procedures, and multi-server operations.
StackX Role Conventions
Role Suffixes
Role Suffixes| Suffix | Use |
|---|
| -dev | Development |
|---|
| -stg | Staging / preproduction |
|---|
| -bkp | Backup |
|---|
| -prd | Production |
|---|
| -drs | Disaster Recovery (DR) |
|---|
| -vip | Failover IP / VIP when included in the architecture |
|---|
Hostcodes and Naming
Hostcodes and Naming| Element | Principle |
|---|
| Generated hostcode | Short code generated automatically to identify a machine without exposing unnecessary business information |
|---|
| Selected hostcode | Prefix defined with the client when the fleet or operations require a stable convention |
|---|
| PRD / DRS pair | Same logical prefix completed by -prd and -drs when two machines form a production / recovery pair |
|---|
| Large client fleet | Client prefix, role, and optionally a sequence number to keep naming easy to read at scale |
|---|
Dedicated Client Templates
Dedicated Client Templates| Principle | What it provides |
|---|
| StackX templates | Reproducible, maintainable, and consistent deployments across machines within the same scope |
|---|
| Sufficient fleet size | Option to design a dedicated template when the volume, contract, or operating constraints warrant it |
|---|
| Client-specific requirements | Tailored preinstallation and settings without exposing the client’s internal conventions |
|---|
| Controlled change | Changes that can be tested, then applied progressively according to the approved scope |
|---|
Relationship to StackX Products
Relationship to StackX Products| Product / scope | Use of conventions |
|---|
| StackX LAMP | Application environments, versions, vhosts, and associated services |
|---|
| StackX Bastion | sxconnect / sxparallel inventory, roles, tags, batch operations, and operator access |
|---|
| StackX Proxy | Dedicated or shared proxies, by project, zone, or client |
|---|
| Replication / Disaster Recovery | Clear identification of -prd and -drs nodes, failover and failback procedures |
|---|
| Backup | -bkp nodes or dedicated backup servers, depending on the architecture |
|---|
These conventions remain adaptable.
They provide a common framework, but can be adjusted for a client, an industry, an existing fleet, or a dedicated template when doing so genuinely improves operations.