What happens on deploy
The first successful ZIP deployment creates Release 1 and sets it as the Box current Release. Later ZIP uploads create the next Box-local Release number.
The stable hosted URL points to the active Box content. Release-scoped URLs are for inspecting a selected historical Release and remain immutable.
Deploy an update
- Open the Box editor and go to its deployment or Releases controls.
- Upload one new ZIP archive.
- Wait for the Release to become ready, then verify the hosted URL.
- Use the Release history to compare the current and prior deployment records.
Tips and limits
- A Release number is the user-facing version for that Box. Database record IDs are internal and should not be used as release labels.
- Do not edit a Release directory to update a site. Upload another ZIP or use Live Workspace where appropriate.
Restore a ready Release
A ready historical Release can be made current. This is a pointer change: the historical bytes stay unchanged.
- Open the Release history for the Box.
- Choose a ready historical Release.
- Make it active, then check the stable hosted URL.