superfly · andie787 · Aug 23, 2024 · Aug 23, 2024 · Aug 23, 2024
diff --git a/apps/going-to-production.html.markerb b/apps/going-to-production.html.markerb
@@ -9,10 +9,10 @@ redirect_from:
   - /docs/reference/going-to-production/
 ---
 
-This checklist guides you through setting up a production environment on Fly.io. What makes an app production-ready can vary from one framework to another. You'll need to decide which checklist items work for your app and setup; not all of the items will apply and there may be other considerations not listed here.
+Use this checklist to help you set up a production environment on Fly.io.
 
 <div class="important icon">
-**Important:** This list is neither exhaustive nor mandatory, and does not guarantee production-readiness for your app. Apps might have unique requirements for production.
+**Important:** The checklist is not exhaustive and does not guarantee production-readiness for your app. Apps can have unique requirements for production depending on the framework and type of app. Some items won't be applicable and there may be other considerations not listed here; you'll need to decide which checklist items work for your app.
 </div>
 
 ## Security

diff --git a/apps/index.html.markerb b/apps/index.html.markerb
@@ -31,9 +31,9 @@ _Store sensitive data, like usernames and passwords, as secrets in your app. Sec
 
 _Get your app ready for production on Fly.io._
 
-- [Going to production with your app](/docs/apps/going-to-production/)
+- [Going to production checklist](/docs/apps/going-to-production/)
 - [App availability and resiliency](/docs/apps/app-availability/)
-- [Tips to fine-tune and (not) benchmark your app on Fly.io](/docs/apps/fine-tune-apps/)
+- [Fine-tune your app](/docs/apps/fine-tune-apps/)
 - [Guidelines for concurrency settings](/docs/apps/concurrency/)
 
 ---

diff --git a/blueprints/autostart-internal-apps.html.md b/blueprints/autostart-internal-apps.html.md
@@ -97,7 +97,7 @@ Here's an example `fly.toml` snippet:
 **Important:** Set `force_https = false`; Flycast only works over HTTP. HTTPS isn't necessary because all your private network traffic goes through encrypted WireGuard tunnels.
 </div>
 
-Learn more about [Fly Launch configuration](/docs/reference/configuration/) and [Fly Proxy autostop/autostart](/docs/launch/autostop-autostart/).
+Learn more about [app configuration](/docs/reference/configuration/) and [Fly Proxy autostop/autostart](/docs/launch/autostop-autostart/).
 
 ### Make sure your app binds to `0.0.0.0:<port>`
 

diff --git a/getting-started/index.html.md b/getting-started/index.html.md
@@ -9,7 +9,7 @@ Get up and running on Fly.io:
 
 - **[Quickstart](/docs/getting-started/launch/):** Launch your own app now.
 
-- **[Launch a demo app](/docs/hands-on/):** Walk through installing the flyctl command-line tool and creating an account, then launch a simple "hellofly" demo app.
+- **[Launch a demo app](/docs/getting-started/launch-demo):** Walk through installing the flyctl command-line tool and creating an account, then launch a simple "hellofly" demo app.
 
 - **[Choose your language or framework](/docs/getting-started/get-started-by-framework/):** Get started on Fly.io with the tech _you_ love.
 
@@ -22,6 +22,7 @@ Get up and running on Fly.io:
 ## Learn more
 
 * [Fly Launch](/docs/apps): You've tried the `fly launch` command. Now learn how to use all the Fly Launch features that help you manage and run your apps.
+* [Going to production checklist](/docs/apps/going-to-production/): Considerations for setting up a production environment on Fly.io.
 * [Fly.io Blueprints](/docs/blueprints/): A library of patterns and examples that you can apply in your own projects.
 * [Databases & Storage](/docs/database-storage-guides/): Options for persistent data storage on Fly.io.
 * [Fly Machines](/docs/machines/): Go deeper with our fast-launching VMs, and use them to run your projects and tasks.

diff --git a/getting-started/troubleshooting.html.md b/getting-started/troubleshooting.html.md
@@ -42,7 +42,7 @@ Any failures in the `fly doctor` output point to where you can start troubleshoo
 
 ### Review your `fly.toml` configuration
 
-Double-check the formatting and configuration options in your `fly.toml` file. Besides [checking port numbers](#warning-the-app-is-listening-on-the-incorrect-address-host-and-port-checking), you should also review any recent changes and make sure you're following the conventions described in [Fly Launch configuration](/docs/reference/configuration/).
+Double-check the formatting and configuration options in your `fly.toml` file. Besides [checking port numbers](#warning-the-app-is-listening-on-the-incorrect-address-host-and-port-checking), you should also review any recent changes and make sure you're following the conventions described in the [app configuration](/docs/reference/configuration/) docs.
 
 ## Get more information about failures
 

diff --git a/index.html.md b/index.html.md
@@ -8,7 +8,7 @@ nav: firecracker
 
 <div class="index-page">
 
-## Get started
+## Get started 
 
 Try our [quickstart or demo app](/docs/getting-started/)
 
@@ -20,7 +20,12 @@ Or choose your favorite [language or framework](/docs/getting-started/get-starte
 
 _Fly Launch is app configuration, provisioning, deployment, scaling, and orchestration with our flyctl CLI._
 
-[Work with your apps](/docs/apps/): create, configure, deploy, and scale with Fly Launch, set secrets, and prepare for production
+[Create and manage apps](/docs/apps/)
+
+[Going to production checklist](/docs/apps/going-to-production/)
+
+[App config (fly.toml)](/docs/reference/configuration/)
+
 
 ---
 
@@ -36,16 +41,10 @@ flyctl is [open source](https://github.com/superfly/flyctl+external)
 
 ## Fly Machines
 
-_Machines are fast-launching VMs—and the compute engine of the Fly.io platform._
+_Machines are fast-launching VMs—and the compute engine of the Fly.io platform. Get precise, low-level control of Machines with our REST API_
 
 Learn all about [Fly Machines](/docs/machines/)
 
----
-
-## Machines API
-
-_Get precise, low-level control of Machines with our REST API._
-
 [Machines API docs](/docs/machines/api/)
 
 ---
@@ -62,12 +61,12 @@ _Run GPU workloads on Fly Machines._
 
 _Services from Fly.io and our extension partners to help you run your entire stack near your users._
 
-[Upstash for Redis®](/docs/upstash/redis/)
-
 [Tigris object storage](/docs/tigris/)
 
 [Supabase Postgres (public alpha)](/docs/supabase/)
 
+[Upstash for Redis®](/docs/upstash/redis/)
+
 [LiteFS - Distributed SQLite](/docs/litefs/)
 
 [Fly Kubernetes (private beta)](/docs/kubernetes/)
@@ -76,9 +75,13 @@ _Services from Fly.io and our extension partners to help you run your entire sta
 
 ## Networking
 
-_Private networking, public networking, custom domains and certificates, UDP apps, and routing._
+_Networking on Fly.io._
+
+[Private networking](/docs/networking/private-networking)
+
+[Public networking](/docs/networking/services)
 
-[Networking](/docs/networking/) on Fly.io
+[Custom domains](/docs/networking/custom-domain/)
 
 ---
 

diff --git a/launch/continuous-deployment-with-github-actions.html.md b/launch/continuous-deployment-with-github-actions.html.md
@@ -141,7 +141,7 @@ This step `uses` the [superfly/flyctl-actions action](https://github.com/marketp
 
 This pulls the API token from GitHub's secrets engine and puts it into the environmental variables passed to the action.
 
-**Step 9** pushes your two new files to the repository: `fly.toml`, the Fly Launch configuration file, and `fly.yml`, the GitHub action file. The push triggers your first automatic deploy. The GitHub action now triggers a redeploy each time you push changes to your repo.
+**Step 9** pushes your two new files to the repository: `fly.toml`, the app configuration file, and `fly.yml`, the GitHub action file. The push triggers your first automatic deploy. The GitHub action now triggers a redeploy each time you push changes to your repo.
 
 ## Conclusion and further reading
 

diff --git a/launch/volume-storage.html.markerb b/launch/volume-storage.html.markerb
@@ -166,7 +166,7 @@ The volume is mounted in the directory specified by the `destination` field in t
 ## Related topics
 
 - [Fly Volumes overview](/docs/volumes/overview/)
-- [`mounts` section](/docs/reference/configuration/#the-mounts-section) in the `fly.toml` Fly Launch configuration file
+- [`mounts` section](/docs/reference/configuration/#the-mounts-section) in the `fly.toml` app configuration file
 - [Create and manage volumes](/docs/volumes/volume-manage/)
 - [Manage volume snapshots](/docs/volumes/snapshots/)
 - [Scale an app with volumes](/docs/apps/scale-count/#scale-an-app-with-volumes)
diff --git a/partials/_apps_nav.html.erb b/partials/_apps_nav.html.erb
@@ -14,7 +14,6 @@
         { text: "Move an app between orgs", path: "/docs/apps/move-app-org/" }
       ]
     },
-    { text: "App Config (fly.toml)", path: "/docs/reference/configuration/", type: "singleton" },
     {
       title: "Fly Launch",
       path: "/docs/launch/",

diff --git a/partials/_firecracker_nav.html.erb b/partials/_firecracker_nav.html.erb
@@ -33,7 +33,7 @@
 
         { text: "Secrets", path: "/docs/apps/secrets/" },
 
-        { text: "Production Apps", path: "/docs/apps/going-to-production/" }
+        { text: "Production Checklist", path: "/docs/apps/going-to-production/" }
       ]
     },
     {

diff --git a/reference/configuration.html.markerb b/reference/configuration.html.markerb
@@ -1,10 +1,10 @@
 ---
-title: Fly Launch configuration (fly.toml)
+title: App configuration (fly.toml)
 layout: docs
 nav: firecracker
 ---
 
-You can configure an app for deployment on Fly.io using a `fly.toml` file. Configuration of builds, environment variables, internet-exposed services, disk mounts, and release commands go here.
+You can configure an app for deployment on Fly.io using a `fly.toml` file. Configuration of builds, environment variables, internet-exposed services, disk mounts, and release commands go here. `fly.toml` configuration applies for apps managed by [Fly Launch commands](/docs/launch/).
 
 ## App configuration files
 

diff --git a/reference/fly-launch.html.md b/reference/fly-launch.html.md
@@ -36,7 +36,7 @@ Build information is in the `build` section of `fly.toml`. `fly launch` will f
 
 Reference: [Builders and Fly.io](/docs/reference/builders/)
 
-## Fly Launch configuration
+## Fly App configuration
 
 On creation, an app gets a default configuration that will work for most basic web apps.
 
@@ -46,7 +46,7 @@ You can make configuration changes by editing an app's `fly.toml` and then runni
 
 The flyctl language-specific scanners make changes to app configuration as part of their work.
 
-Reference: [Fly Launch configuration (fly.toml)](/docs/reference/configuration/)
+Reference: [App configuration (fly.toml)](/docs/reference/configuration/)
 
 ## Platform resource provisioning
 

diff --git a/reference/index.html.md b/reference/index.html.md
@@ -20,7 +20,7 @@ Quick references for often-used resources like flyctl and `fly.toml`. Or dig a l
 
 * **[flyctl](/docs/flyctl/):** The flyctl CLI reference documentation.
 
-* **[App Configuration (fly.toml)](/docs/reference/configuration/):** The settings for configuring your app in the `fly.toml` configuration file. The Fly Launch configuration includes how the app is built, its volume mounts, network services, and more.
+* **[App Configuration (fly.toml)](/docs/reference/configuration/):** The settings for configuring your app in the `fly.toml` configuration file. The app configuration includes how the app is built, its volume mounts, network services, and more.
 
 * **[Fly Launch](/docs/reference/fly-launch/):** A deeper dive into how Fly Launch creates and configures new apps.