Skip to main content
The Staging Detail page is the control panel for one dryrun environment. You reach it from the green View action on a dryrun row in the Dryrun Environments tab, or from the View action on the Staging Environments tab inside Project Overview. The URL pattern is: 
/v2/apps/dryrunpro/staging/<staging_id>
where <staging_id> is the integer DryRunPro assigned at create time (e.g. 14). This page documents every panel on the Staging Detail screen: the header with build action buttons, the Server Connection panel, the Status / build steps log, the CDN Mode selector, the Docker Container fleet card, the Container SSH Access card with key generation, and the Docker Logs download. The page title is the dryrun name plus the suffix ” - Dryrun environment”, e.g. “Xupes Downgrade Branch - Dryrun environment”. A small caption under the title shows three pieces of metadata:
  • Created by: the DryRunPro user who triggered the create.
  • Started: the build start timestamp (e.g. 2026-04-08 11:42:48).
  • Ended: the build end timestamp (e.g. 2026-04-08 12:34:48).
To the right of the metadata sits a link captioned “Site-Wide Analysis Tool” that opens the SWAT report in a new tab.

​
Action button bar

Six purple action buttons sit directly below the header, in a horizontal strip:
  1. Execute CLI, opens an interactive Cloud CLI shell scoped to this dryrun. You can run any magento-cloud command without context-switching.
  2. Generate Docker Snapshot, packages the running container set into a downloadable Docker snapshot (.tar.gz) and adds it to the Docker packages tab.
  3. Generate Warden Package, exports the dryrun as a Warden-compatible local development bundle for laptop-side debugging.
  4. Code Audit, runs a code-quality pass and surfaces results in a panel.
  5. Install Extension, opens a search-and-install dialog for Magento extensions.
  6. Re-Sync, re-pulls the database and media from the source environment without rebuilding the codebase. Use when production data has drifted and you want the dryrun to reflect the latest state.
  7. SWAT Report, regenerates the SWAT report on demand.

​
Server connection panel

A two-column information block on the left side of the page. The header strip shows the environment role (e.g. “Production”) and the auto-detection badge (“Auto”). Underneath:
  • Server host: the AWS hostname (e.g. 144.126.230.146).
  • Server port: typically 2222.
  • Server username: a long opaque handle generated by Adobe Cloud (e.g. 2k77747a3uyxkiwaplhn-staging).
  • Access database: a Click here link that opens phpMyAdmin or the equivalent DB browser scoped to the dryrun’s database.
  • License Key: an opaque handle for the running build (e.g. f8c777bf882e02816).
  • Database password: a copy-to-clipboard masked field.
This is the connection bundle an engineer needs to SSH into the running container fleet, browse the database, and run debug commands.

​
Status panel

A vertical list of build steps, each with a green tick (success) or red cross (failure), each with a “View Log” link on the right. The default Adobe Commerce Cloud build pipeline produces these eight steps:
  1. Initialisation cleanup (ports)
  2. Get PHP version from Server
  3. Extract docker common package
  4. Sync source code (rsync)
  5. Configure docker container
  6. Create Docker container
  7. Start container
  8. Verify containers running
A green “Docker Container Creation Steps” header sits at the top. Each step’s View Log link expands an inline pane with the full stdout/stderr of that step. Useful for diagnosing a Failed dryrun: scroll to the first red cross and read the log.

​
CDN mode selector

A configuration block titled CDN mode with a dropdown (“None (default DRP behaviour)” by default) and a tickbox captioned “Apply changes to .env config + docker refresh + finalize”. The dropdown lets you switch the dryrun’s CDN behaviour:
  • None (default DRP behaviour): DryRunPro’s bundled CDN entry, served via Fastly, with no further config.
  • Fastly Magento mode: Applies the dryrun’s CDN config to look like Adobe-side Fastly (VCL profile, surrogate keys, Magento module).
  • Cloudflare Magento mode: Applies the dryrun’s CDN config to look like Cloudflare for Magento (page rules, cache invalidation hooks).
  • Pass-through: No CDN, requests hit Magento directly. Use only for low-traffic dryruns (bot checks, smoke tests).
Click the blue Save button on the right to apply. DryRunPro updates the env, refreshes the docker container, and the new CDN mode takes effect within a minute. See Settings, CDN for the tenancy-level CDN credentials this draws from.

​
Docker container fleet card

Below the CDN block, a green “running” badge and a card titled Docker container that lists every container in the dryrun’s fleet:
  • Apache
  • MySQL
  • Redis
  • OpenSearch
  • RabbitMQ
Each container has a “View Details” link that expands into status, port, image hash, restart policy, and resource usage. Two action buttons sit underneath:
  • Start containers (green): bring all containers up.
  • Stop containers (red): shut all containers down. The dryrun stays defined and resumable; the URL stops resolving until you start again.
Stopping is useful for parking a dryrun overnight without tearing it down (the build state is preserved, only the running compute is reclaimed).

​
Container SSH access card

A purple card titled Container SSH access with the connection options listed across the top:
  • PuTTY
  • FileZilla
  • OpenSSH
Below the heading, a “SSH KEYS GENERATED” counter (e.g. 142) and a green Generate Key button. Clicking Generate Key produces a fresh RSA key pair scoped to this dryrun and shows:
  • The fingerprint.
  • The user (e.g. ubuntu).
  • The private key (downloadable as a .pem).
The card also displays a status note (e.g. “Notice: New key generated”) under the button. This is how engineers SSH into the dryrun container fleet directly. Each key is scoped to one engineer and one dryrun; revoking is a button on the keys list.

​
Docker logs

At the bottom of the page, a “Docker Logs” caption with a Download link. Click to download the consolidated log bundle (build steps + container stdout) as a .tar.gz for offline analysis or attaching to a support ticket.

​
When you would visit this page

  • After spinning up a new dryrun, to grab the URL and the database credentials.
  • When a dryrun fails, to read the per-step build log and diagnose.
  • When QA reports a bug on the dryrun, to SSH in and inspect.
  • When you want to switch CDN mode (e.g. to validate Fastly cache behaviour before promoting to production).
  • When you need to generate a Docker snapshot for hand-off to Adobe support.
  • When you want to install a Magento extension on the dryrun for testing.

​
Frequently asked questions

Can I share my SSH key with a colleague? Technically yes (it is a private key on disk) but it is not recommended. Each engineer should generate their own key from this page. Revocation is per-key, so personal keys make it easier to off-board a single engineer without locking out the whole team. The Server connection panel says “Production”. Is the dryrun running against production? The Production label refers to the source environment that was cloned, not where the dryrun is running. The dryrun itself is an isolated container fleet. Cloning from production simply means the dryrun has production data; it does not mean it can write back to production. What does Re-Sync do? Re-pulls the source environment’s database and media into the dryrun without rebuilding the codebase. The dryrun’s branch and Composer state stay as they were. Useful when production data has drifted and you want the dryrun to mirror the latest reality. Can I install a Magento extension on the dryrun? Yes, via the Install Extension action button in the header strip. The extension is composer-installed into the dryrun, the env config is updated, and the container is refreshed. The change is local to this dryrun and does not propagate to the Adobe-side project. My CDN mode change did not take effect. Make sure the “Apply changes to .env config + docker refresh + finalize” tickbox is ticked when you click Save. Without it the dropdown change is saved to the database but not applied to the live container. Untick the box only if you want to stage the config without bouncing the container. Why is the SWAT report still Processing 30 minutes after my build completed? SWAT runs static analysis across the entire codebase plus Magento extension audit. For projects with deep extension stacks, 30 to 60 minutes is normal. If it stays Processing for over an hour, open a ticket. Can I extend the dryrun’s expiry date? Yes. Edit the dryrun (red Edit action on the Dryrun Environments tab) and set a new expiry. Some agency tenancies enforce a maximum lifetime via tenancy settings; if you cannot extend, ask your tenancy admin. Where is the Docker snapshot stored after Generate Docker Snapshot? On the Docker packages tab, with a download link. The snapshot is retained until you delete it manually or until the parent project is deleted.