Hosting Operations
Rollback a Release Symlink in a Sandbox
You need to rehearse a symlink-style rollback by pointing current at the previous stable release directory.
Command
cd /lab/git-recovery-rollback && ln -sfn 2026-06-25-1000 releases/currentWhat changed
The releases/current symlink inside the disposable fixture points to 2026-06-25-1000.
Danger
caution
When to use it
Use in a sandbox or controlled deploy path when rollback is implemented by moving a current symlink.
When not to use it
Do not run this against a real production releases directory unless your deployment process explicitly calls for it.
Undo or recovery
Point releases/current back to 2026-06-25-1030 or recreate the fixture.
Expected output
The current symlink resolves to 2026-06-25-1000 and its VERSION status is stable.
demo script
Disposable terminal steps
cd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSIONcd /lab/git-recovery-rollback && ln -sfn 2026-06-25-1000 releases/currentcd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSION
simulated output
What it looks like
::fixture-ready::
$ 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
$ cd /lab/git-recovery-rollback && ln -sfn 2026-06-25-1000 releases/current
::exit-code::0
$ cd /lab/git-recovery-rollback && readlink releases/current && cat releases/current/VERSION
2026-06-25-1000
release=2026-06-25-1000
status=stable
::exit-code::0
YouTube Short
Rollback the symlink safely.
In this sandbox, rollback is just moving current to the last stable release. Practice it before production pressure.
LinkedIn hook
Practice the pointer switch where the blast radius is zero.
Question: Have you rehearsed your symlink rollback command outside production?
experiments
A/B tests to run
Metric: comment_rate
A: Practice pointer rollback safely.
B: Move current only when you know the target.