Hosting Operations

Check the Active Release Symlink

A deployment uses release directories and a current symlink, and you need to confirm which release is active.

Command

cd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSION

What changed

Nothing changes. The symlink target and release metadata are printed.

Danger

safe

When to use it

Use during deploy or rollback triage when production is selected by a filesystem pointer.

When not to use it

Do not assume Git HEAD and the active release symlink always match.

Undo or recovery

No undo needed because this command is read-only.

Expected output

The current symlink target and VERSION file for release 2026-06-25-1030.

demo script

Disposable terminal steps

cd /lab/git-recovery-rollback && ls -l releases/current
cd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSION

Terminal transcript Demo JSON

simulated output

What it looks like

disposable vessel

::fixture-ready::
$ cd /lab/git-recovery-rollback && ls -l releases/current
lrwxrwxrwx 1 root root 15 Jun 26 00:27 releases/current -> 2026-06-25-1030
::exit-code::0
$ cd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSION
2026-06-25-1030
release=2026-06-25-1030
status=suspect
::exit-code::0

YouTube Short

Which release is active?

If deploys use a current symlink, inspect that pointer directly. Git history is only part of the incident.

experiments

A/B tests to run

Metric: save_rate

A: Git is not the only deployment state.

B: Check the active release pointer.