Document destroy force release as also destroying the cache

BastilleBSD · Dec 16, 2024 · bc54c30 · bc54c30
1 parent fb21ff1
commit bc54c30
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 1 deletion.
diff --git a/docs/chapters/subcommands/destroy.rst b/docs/chapters/subcommands/destroy.rst
@@ -17,3 +17,11 @@ created.  Note: containers must be stopped before destroyed.
   Deleting Container: folsom.
   Note: containers console logs not destroyed.
   /usr/local/bastille/logs/folsom_console.log
+
+Release can be destroyed provided there are no child jails. The `force` option
+deletes the release cache directory as well:
+
+.. code-block:: shell
+
+  ishmael ~ # bastille destroy force 14.0-RELEASE
+  Deleting base: 14.0-RELEASE
diff --git a/docs/chapters/upgrading.rst b/docs/chapters/upgrading.rst
@@ -38,4 +38,6 @@ After upgrading all jails from one release to the next you may find that you now
 
 `bastille list releases` to list all bootstrapped releases.
 
-`bastille destroy X.Y-RELEASE` to fully delete the release. 
+`bastille destroy X.Y-RELEASE` to fully delete the release.
+
+`bastille destroy force X.Y-RELEASE` to delete the cache directory as well.