From 085002781e38fc362c1d72e0a28cc80c4ce699cd Mon Sep 17 00:00:00 2001 From: andie787 <4andie@gmail.com> Date: Wed, 27 Sep 2023 15:21:16 -0400 Subject: [PATCH] final changes and revert to old nav --- apps/volume-manage.html.markerb | 4 +-- apps/volume-storage.html.markerb | 10 ++++--- partials/_volumes_nav.html.erb | 47 -------------------------------- reference/volumes.html.markerb | 6 ++-- volumes/index.html.markerb | 4 +-- 5 files changed, 13 insertions(+), 58 deletions(-) delete mode 100644 partials/_volumes_nav.html.erb diff --git a/apps/volume-manage.html.markerb b/apps/volume-manage.html.markerb index c3064baf82..2922d39967 100644 --- a/apps/volume-manage.html.markerb +++ b/apps/volume-manage.html.markerb @@ -1,13 +1,13 @@ --- title: Manage volume storage layout: docs -nav: volumes +nav: firecracker order: 40 --- Manage Fly Volumes using the [`fly volumes`](/docs/flyctl/volumes/) command. -
**Note**: `fly volumes` is aliased to `fly volume` and `fly vol`.
+
**Note**: `fly volumes` is aliased to `fly volume` and `fly vol`.
## Create a volume diff --git a/apps/volume-storage.html.markerb b/apps/volume-storage.html.markerb index 06ae465739..8729bb521c 100644 --- a/apps/volume-storage.html.markerb +++ b/apps/volume-storage.html.markerb @@ -1,7 +1,7 @@ --- title: Add volume storage layout: docs -nav: volumes +nav: firecracker order: 30 --- @@ -9,9 +9,9 @@ Fly Volumes are local persistent storage for [Fly Machines](/docs/machines/). Le ## Launch a new app with a Fly Volume -Launch a new app with one Machine and an attached volume, and then clone the Machine to scale out. +Use [Fly Launch](/docs/apps/) to create a new app with one Machine and an attached volume, and then clone the Machine to scale out. -1. Launch a new app, and type `N` at the "deploy now?" prompt: +1. Launch a new app from your project source directory, and type `N` at the "deploy now?" prompt: ```cmd fly launch @@ -41,7 +41,7 @@ Launch a new app with one Machine and an attached volume, and then clone the Mac 1. [Confirm that the volume is attached to a Machine](#confirm-the-volume-is-attached-to-a-machine). -1. (Recommended) Clone the first Machine to scale out to two Machines with volumes: +1. (Recommended if your app handles replication) Clone the first Machine to scale out to two Machines with volumes: ```cmd fly machine clone @@ -66,6 +66,8 @@ Launch a new app with one Machine and an attached volume, and then clone the Mac ## Add volumes to an existing app +Add a volume to an app created with [Fly Launch](/docs/apps/). + 1. Add a [`[mounts]` section](/docs/reference/configuration/#the-mounts-section) in the app's `fly.toml`, where `source` is the volume name and `destination` is the directory where the volume should be mounted on the Machine file system. For example: ```toml diff --git a/partials/_volumes_nav.html.erb b/partials/_volumes_nav.html.erb deleted file mode 100644 index 942b207ac7..0000000000 --- a/partials/_volumes_nav.html.erb +++ /dev/null @@ -1,47 +0,0 @@ - - - - diff --git a/reference/volumes.html.markerb b/reference/volumes.html.markerb index 19dc05b617..dd477759e8 100644 --- a/reference/volumes.html.markerb +++ b/reference/volumes.html.markerb @@ -1,7 +1,7 @@ --- title: Fly Volumes overview layout: docs -nav: volumes +nav: firecracker order: 20 --- @@ -24,8 +24,8 @@ If volumes don't work for your use case, then explore other options for data sto ## Volume redundancy -
-Always run at least two volumes per app. We usually recommend running at least two Machines per app to increase availability, and if you're using volumes, then each machine should have an attached volume. If you only have one Machine and volume, then you'll have downtime if there's a host or network failure, and whenever you deploy your app. Also remember that volumes don't have built-in replication between them. +
+Important: Always run at least two volumes per app. We usually recommend running at least two Machines per app to increase availability, and if you're using volumes, then each machine should have an attached volume. If you only have one Machine and volume, then you'll have downtime if there's a host or network failure, and whenever you deploy your app. Also remember that volumes don't have built-in replication between them.
In a few cases, you can run a single Machine with an attached volume. For example, if you're running an app with a standard SQLite database, or your app is in development and you're not yet worried about downtime. diff --git a/volumes/index.html.markerb b/volumes/index.html.markerb index 2dc2a70c3c..392e3d519d 100644 --- a/volumes/index.html.markerb +++ b/volumes/index.html.markerb @@ -1,7 +1,7 @@ --- title: "Fly Volumes" layout: docs -nav: volumes +nav: firecracker toc: false order: 10 --- @@ -22,7 +22,7 @@ Get things done with volumes. [Manage volume storage](/docs/apps/volume-manage/) -More volume how-tos: +Related how-tos: [Scale an app with volumes](/docs/apps/scale-count/#scale-an-app-with-volumes)