Rollbacks & history

Every jekyo up records a revision. Going back is one command, not an archaeology project.

History

jekyo history shop
REVISION  DEPLOYED
v1        2d ago
v2        5h ago
v3        10m ago

Revisions live in the cluster itself (not on your laptop), so any machine with the context sees the same history.

Rolling back

jekyo rollback shop        # to the previous revision
jekyo rollback shop v1     # to a specific one

A rollback re-applies the stored manifests of the target revision and records the result as a new revision. History moves forward, always. Volumes are untouched: rolling back the code never touches the data.

Restarting

Sometimes you don't need a different version, just fresh pods:

jekyo restart shop          # rolling restart, whole app
jekyo restart shop/api      # one service

Rolling means no downtime for multi-replica services: new pods come up and pass health checks before old ones go away.