move kv files

_components/Feedback.tsx

@@ -117,7 +117,7 @@ export default function Feedback({ file }: { file: string | undefined }) {
                 rel=""
                 class="mt-4 !underline underline-offset-2 text-xs block"
                 target="_blank"
-                href="/deploy/privacy-policy"
+                href="/deploy/privacy_policy"
               >
                 Privacy policy
               </a>

_components/Footer.tsx

@@ -151,7 +151,7 @@ const data = [
       },
       {
         label: "Privacy Policy",
-        href: "/deploy/privacy-policy",
+        href: "/deploy/privacy_policy",
       },
     ],
   },

_config.ts

@@ -137,9 +137,9 @@ site.copy("timeUtils.ts");
 site.copy("subhosting/api/images");
 site.copy("deploy/docs-images");
 site.copy("deploy/images");
-site.copy("deploy/kv/manual/images");
+site.copy("deploy/classic/images");
+site.copy("deploy/kv/images");
 site.copy("deploy/tutorials/images");
-site.copy("deploy/kv/tutorials/images");
 site.copy("runtime/fundamentals/images");
 site.copy("runtime/getting_started/images");
 site.copy("runtime/reference/images");

data.json

@@ -14,7 +14,7 @@
     "category": "Runtime"
   },
   {
-    "path": "/deploy/pricing-and-limits/#tls-proxying",
+    "path": "/deploy/pricing_and_limits/#tls-proxying",
     "title": "TLS proxying",
     "content": "TLS termination is required for outgoing connections to port 443 (the port used\nfor HTTPS). Using Deno.connect to\nconnect to these ports is prohibited. If you need to establish a TLS connection\nto port 443, please use\nDeno.connectTls instead. fetch is\nnot impacted by this restriction.\nThis restriction is in place because connecting to port 443 without terminating\nTLS is frequently used in TLS-over-TLS proxies, which are prohibited on Deno\nDeploy as per our acceptable use policy.\n",
     "section": "Pricing and limitations",

deploy/_data.ts

@@ -32,7 +32,7 @@ export const sidebar = [
       },
       {
         title: "Environment Variables and Contexts",
-        href: "/deploy/reference/env-vars-and-contexts/",
+        href: "/deploy/reference/env_vars_and_contexts/",
       },
       {
         title: "Timelines",
@@ -48,15 +48,15 @@ export const sidebar = [
       },
       {
         title: "Deno KV",
-        href: "/deploy/reference/deno-kv/",
+        href: "/deploy/reference/deno_kv/",
       },
       {
         title: "Databases",
         href: "/deploy/reference/databases/",
       },
       {
         title: "Cloud Connections",
-        href: "/deploy/reference/cloud-connections/",
+        href: "/deploy/reference/cloud_connections/",
       },
       {
         title: "OIDC",
@@ -84,6 +84,29 @@ export const sidebar = [
       },
     ],
   },
+  {
+    title: "KV",
+    items: [
+      { title: "Overview", href: "/deploy/kv/" },
+      { title: "Key space", href: "/deploy/kv/key_space/" },
+      { title: "Operations", href: "/deploy/kv/operations/" },
+      {
+        title: "Key expiration",
+        href: "/deploy/kv/key_expiration/",
+      },
+      {
+        title: "Secondary indexes",
+        href: "/deploy/kv/secondary_indexes/",
+      },
+      { title: "Transactions", href: "/deploy/kv/transactions/" },
+      { title: "Node", href: "/deploy/kv/node/" },
+      {
+        title: "Data modeling",
+        href: "/deploy/kv/data_modeling_typescript/",
+      },
+      { title: "Backup", href: "/deploy/kv/backup/" },
+    ],
+  },
   {
     title: "Policies and Limits",
     items: [
@@ -93,17 +116,17 @@ export const sidebar = [
       },
       {
         title: "Acceptable Use Policy",
-        href: "/deploy/acceptable-use-policy/",
+        href: "/deploy/acceptable_use_policy/",
       },
       {
         title: "Fulfillment Policy",
-        href: "/deploy/fulfillment-policy/",
+        href: "/deploy/fulfillment_policy/",
       },
-      { title: "Privacy Policy", href: "/deploy/privacy-policy/" },
+      { title: "Privacy Policy", href: "/deploy/privacy_policy/" },
       { title: "Security", href: "/deploy/security/" },
       {
         title: "Terms and Conditions",
-        href: "/deploy/terms-and-conditions/",
+        href: "/deploy/terms_and_conditions/",
       },
     ],
   },

deploy/changelog.md

@@ -103,7 +103,7 @@ description: "Listing notable progress in the development and evolution of Deno
     you through the process of connecting your app to AWS or GCP.
   - You can use the standard AWS and GCP SDKs to access the services - no need
     to re-write any code to use a different API.
-  - [Learn more in the documentation.](/deploy/reference/cloud-connections/)
+  - [Learn more in the documentation.](/deploy/reference/cloud_connections/)
 - The application metrics page now shows more metrics, including V8 memory
   metrics such as heap size and garbage collection stats, as well as process
   level metrics such as CPU usage and overall memory usage.

deploy/classic/_data.ts

@@ -19,7 +19,7 @@ export const sidebar = [
           { title: "Regions", href: "/deploy/classic/regions/" },
           {
             title: "Pricing and limits",
-            href: "/deploy/pricing-and-limits/",
+            href: "/deploy/pricing_and_limits/",
           },
         ],
       },
@@ -48,36 +48,13 @@ export const sidebar = [
         title: "Logs",
         href: "/deploy/classic/logs/",
       },
-      {
-        title: "KV",
-        items: [
-          { title: "Overview", href: "/deploy/kv/manual/" },
-          { title: "Key space", href: "/deploy/kv/manual/key_space/" },
-          { title: "Operations", href: "/deploy/kv/manual/operations/" },
-          {
-            title: "Key expiration",
-            href: "/deploy/kv/manual/key_expiration/",
-          },
-          {
-            title: "Secondary indexes",
-            href: "/deploy/kv/manual/secondary_indexes/",
-          },
-          { title: "Transactions", href: "/deploy/kv/manual/transactions/" },
-          { title: "Node", href: "/deploy/kv/manual/node/" },
-          {
-            title: "Data modeling",
-            href: "/deploy/kv/manual/data_modeling_typescript/",
-          },
-          { title: "Backup", href: "/deploy/kv/manual/backup/" },
-        ],
-      },
       {
         title: "Queues",
-        href: "/deploy/kv/manual/queue_overview/",
+        href: "/deploy/classic/queues/",
       },
       {
         title: "Cron",
-        href: "/deploy/kv/manual/cron/",
+        href: "/deploy/classic/cron/",
       },
       {
         title: "Edge cache",
@@ -90,7 +67,7 @@ export const sidebar = [
     items: [
       {
         title: "Deno KV",
-        href: "/deploy/kv/manual/on_deploy/",
+        href: "/deploy/classic/kv_on_deploy/",
       },
       {
         title: "Third-Party Databases",

deploy/kv/manual/cron.md → deploy/classic/cron.md

@@ -2,6 +2,7 @@
 title: "Scheduling cron tasks"
 oldUrl:
   - /kv/manual/cron/
+  - /deploy/kv/manual/cron/
 ---
 
 :::info Legacy Documentation
@@ -76,7 +77,7 @@ Any nested `Deno.cron` definitions (e.g. inside
 in an error or will be ignored.
 
 If you need to schedule tasks dynamically during your Deno program execution,
-you can use the [Deno Queues](./queue_overview) APIs.
+you can use the [Deno Queues](/deploy/classic/queues/) APIs.
 
 ### Time zone
 

deploy/classic/edge-cache.md → deploy/classic/edge_cache.md

@@ -1,5 +1,7 @@
 ---
 title: "Edge Cache"
+oldUrl:
+  - /deploy/classic/edge-cache/
 ---
 
 :::info Legacy Documentation

deploy/kv/manual/on_deploy.md → deploy/classic/kv_on_deploy.md

@@ -3,6 +3,7 @@ title: "KV on Deno Deploy"
 oldUrl:
   - /deploy/manual/kv/
   - /kv/manual/on_deploy/
+  - /deploy/kv/manual/on_deploy/
 ---
 
 :::info Legacy Documentation
@@ -53,12 +54,6 @@ Below are the latency figures observed in our top regions:
 | California (us-west2)      | 72ms                           | 72ms                         |
 | Hong Kong (asia-east2)     | 42ms                           | 194ms                        |
 
-## Distributed queues
-
-Serverless distributed queues are available on Deno Deploy. See
-[Queues on Deno Deploy](/deploy/kv/manual/queue_overview#queues-on-deno-deploy)
-for more details.
-
 ## Connect to managed databases from outside of Deno Deploy
 
 You can connect to your Deno Deploy KV database from your Deno application

deploy/kv/manual/queue_overview.md → deploy/classic/queues.md

@@ -2,8 +2,17 @@
 title: "Using Queues"
 oldUrl:
   - /kv/manual/queue_overview/
+  - /deploy/kv/manual/queue_overview/
 ---
 
+:::info Legacy Documentation
+
+You are viewing legacy documentation for Deno Deploy Classic. We recommend
+migrating to the new
+<a href="/deploy/">Deno Deploy</a> platform.
+
+:::
+
 <deno-admonition></deno-admonition>
 
 The Deno runtime includes a queueing API that supports offloading larger
@@ -108,8 +117,9 @@ kv.listenQueue((msg: unknown) => {
 
 ## Queue API with KV atomic transactions
 
-You can combine the queue API with [KV atomic transactions](./transactions) to
-atomically enqueue messages and modify keys in the same transaction.
+You can combine the queue API with
+[KV atomic transactions](/deploy/kv/transactions/) to atomically enqueue
+messages and modify keys in the same transaction.
 
 ```ts title="kv_transaction_example.ts"
 const kv = await Deno.openKv();
@@ -160,8 +170,8 @@ It's important to design your applications such that duplicate messages are
 handled correctly.
 
 You may use queues in combination with
-[KV atomic transactions](/deploy/kv/manual/transactions) primitives to ensure
-that your queue handler KV updates are performed exactly once per message. See
+[KV atomic transactions](/deploy/kv/transactions) primitives to ensure that your
+queue handler KV updates are performed exactly once per message. See
 [Queue API with KV atomic transactions](#queue-api-with-kv-atomic-transactions).
 
 ### Automatic retries
@@ -230,9 +240,7 @@ there's no need to wait for the underlying task to be completed before returning
 a response.
 
 In these cases, you can offload work to a queue to keep your web application
-responsive and send immediate feedback to clients. To see an example of this use
-case in action, check out our
-[webhook processing example](../tutorials/webhook_processor.md).
+responsive and send immediate feedback to clients.
 
 ### Scheduling work for the future
 
@@ -242,6 +250,3 @@ to send a notification to a new customer a day after they have placed an order
 to send them a satisfaction survey. You can schedule a queue message to be
 delivered 24 hours into the future, and set up a listener to send out the
 notification at that time.
-
-To see an example of scheduling a notification to go out in the future, check
-out our [notification example](../tutorials/schedule_notification.md).

deploy/kv/manual/backup.md → deploy/kv/backup.md

@@ -2,18 +2,11 @@
 title: "Backups"
 oldUrl:
   - /kv/manual/backup/
+  - /deploy/kv/manual/backup/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
-KV databases hosted on Deno Deploy Classic can be continuously backed up to your
-own S3-compatible storage buckets. This is in addition to the replication and
+KV databases hosted on Deno Deploy can be continuously backed up to your own
+S3-compatible storage buckets. This is in addition to the replication and
 backups that we internally perform for all data stored in hosted Deno KV
 databases to ensure high availability and data durability.
 

deploy/kv/manual/data_modeling_typescript.md → deploy/kv/data_modeling_typescript.md

@@ -2,16 +2,9 @@
 title: "Data Modeling in TypeScript"
 oldUrl:
   - /kv/manual/data_modeling_typescript/
+  - /deploy/kv/manual/data_modeling_typescript/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
 In TypeScript applications, it is usually desirable to create strongly-typed,
 well-documented objects to contain the data that your application operates on.
 Using [interfaces](https://www.typescriptlang.org/docs/handbook/2/objects.html)

deploy/kv/manual/index.md → deploy/kv/index.md

@@ -4,15 +4,16 @@ oldUrl:
   - /kv/
   - /kv/manual/
   - /runtime/manual/runtime/kv/
+  - /deploy/kv/manual/
 ---
 
-**Deno KV** is a
+Deno KV is a
 [key-value database](https://en.wikipedia.org/wiki/Key%E2%80%93value_database)
 built directly into the Deno runtime, available in the
 [`Deno.Kv` namespace](https://docs.deno.com/api/deno/~/Deno.Kv). It can be used
 for many kinds of data storage use cases, but excels at storing simple data
 structures that benefit from very fast reads and writes. Deno KV is available in
-the Deno CLI and on [Deno Deploy](./on_deploy).
+the Deno CLI and on [Deno Deploy](/deploy/reference/deno_kv/).
 
 :::caution
 
@@ -237,15 +238,11 @@ Learn more about [using Deno KV watch here](./operations#watch).
 
 ## Production usage
 
-Deno KV is available for use in live applications on [Deno Deploy](./on_deploy).
-In production, Deno KV is backed by
+Deno KV is available for use in live applications on
+[Deno Deploy](/deploy/reference/deno_kv/). In production, Deno KV is backed by
 [FoundationDB](https://www.foundationdb.org/), the open source key-value store
 created by Apple.
 
-**No additional configuration is necessary** to run your Deno programs that use
-KV on Deploy - a new Deploy database will be provisioned for you when required
-by your code. Learn more about Deno KV on Deno Deploy [here](./on_deploy).
-
 ## Testing
 
 By default, [`Deno.openKv()`](https://docs.deno.com/api/deno/~/Deno.openKv)

deploy/kv/manual/key_expiration.md → deploy/kv/key_expiration.md

@@ -2,6 +2,7 @@
 title: "Key Expiration (TTL for keys)"
 oldUrl:
   - /kv/manual/key_expiration/
+  - /deploy/kv/manual/key_expiration/
 ---
 
 <deno-admonition></deno-admonition>

deploy/kv/manual/key_space.md → deploy/kv/key_space.md

@@ -3,6 +3,7 @@ title: "Key Space"
 oldUrl:
   - /runtime/manual/runtime/kv/key_space/
   - /kv/manual/key_space/
+  - /deploy/kv/manual/key_space/
 ---
 
 <deno-admonition></deno-admonition>

deploy/kv/manual/node.md → deploy/kv/node.md

@@ -4,14 +4,6 @@ oldUrl:
   - /kv/manual/node/
 ---
 
-:::info Legacy Documentation
-
-You are viewing legacy documentation for Deno Deploy Classic. We recommend
-migrating to the new
-<a href="/deploy/">Deno Deploy</a> platform.
-
-:::
-
 Connecting to a Deno KV database in Node.js is supported via our
 [official client library on npm](https://www.npmjs.com/package/@deno/kv). You
 can find usage instructions for this option below.