427 docs rfc add docs about forking services (#4490)

forking

Author: billy-the-fish

_partials/_devops-cli-service-forks.md

@@ -0,0 +1,61 @@
+import CLIINSTALL from "versionContent/_partials/_devops-cli-install.mdx";
+
+To manage development forks:
+
+<Procedure> 
+
+<CLIINSTALL />
+
+1. **Fork the $SERVICE_SHORT**
+
+   ```shell
+    tiger service fork tgrservice --now --no-wait --name bob   
+   ```
+   By default a fork matches the resource of the parent $SERVICE_LONGs. For paid plans specify `--cpu` and/or `--memory` for dedicated resources.
+
+   You see something like:
+
+    ```terminaloutput
+    🍴 Forking service 'tgrservice' to create 'bob' at current state...
+    ✅ Fork request accepted!
+    📋 New Service ID: <service_id>
+    🔐 Password saved to system keyring for automatic authentication
+    🎯 Set service '<service_id>' as default service.
+    ⏳ Service is being forked. Use 'tiger service list' to check status.
+    ┌───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────┐
+    │     PROPERTY      │                                              VALUE                                               │
+    ├───────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────┤
+    │ Service ID        │ <service_id>                                                                                       │
+    │ Name              │ bob                                                                                              │
+    │ Status            │                                                                                                  │
+    │ Type              │ TIMESCALEDB                                                                                      │
+    │ Region            │ eu-central-1                                                                                     │
+    │ CPU               │ 0.5 cores (500m)                                                                                 │
+    │ Memory            │ 2 GB                                                                                             │
+    │ Direct Endpoint   │ <service-id>.<project-id>.tsdb.cloud.timescale.com:<port>                                             │
+    │ Created           │ 2025-10-08 13:58:07 UTC                                                                          │
+    │ Connection String │ postgresql://tsdbadmin@<service-id>.<project-id>.tsdb.cloud.timescale.com:<port>/tsdb?sslmode=require │
+    └───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────┘
+   ```
+
+1. **When you are done, delete your forked $SERVICE_SHORT**
+
+    1. Use the CLI to request $SERVICE_SHORT delete:
+
+       ```shell
+       tiger service delete <service_id>  
+       ```
+    1. Validate the $SERVICE_SHORT delete:
+
+        ```terminaloutput
+        Are you sure you want to delete service '<service_id>'? This operation cannot be undone.
+        Type the service ID '<service_id>' to confirm:
+        <service_id>
+        ```
+       You see something like:
+        ```terminaloutput
+        🗑️  Delete request accepted for service '<service_id>'.
+        ✅ Service '<service_id>' has been successfully deleted.
+        ```
+
+</Procedure>

_partials/_manage-a-data-exporter.md

@@ -109,4 +109,4 @@ It must be one of the following:
 [console-cloudwatch-configuration]: https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups
 [console-cloudwatch-create-group]: https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups/create-log-group
 [services-portal]: https://console.cloud.timescale.com/dashboard/services
-[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
+[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan

_partials/_prometheus-integrate.md

@@ -209,4 +209,4 @@ You can further [visualize your data][grafana-prometheus] with Grafana. Use the
 [enable-timescaledb]: /self-hosted/:currentVersion:/install/
 [prometheus-authentication]: https://prometheus.io/docs/guides/basic-auth/
 [scrape-targets]: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
-[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
+[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan

about/changelog.md

@@ -919,7 +919,7 @@ Highlighted features in TimescaleDB v2.17 are:
 
 ### HIPAA compliance
 
-Timescale Cloud's [Enterprise plan](https://docs.timescale.com/about/latest/pricing-and-account-management/#features-included-in-each-plan) is now HIPAA (Health Insurance Portability and Accountability Act) compliant. This allows organizations to securely manage and analyze sensitive healthcare data, ensuring they meet regulatory requirements while building compliant applications.
+Timescale Cloud's [Enterprise plan](https://docs.timescale.com/about/latest/pricing-and-account-management/#features-included-in-each-pricing-plan) is now HIPAA (Health Insurance Portability and Accountability Act) compliant. This allows organizations to securely manage and analyze sensitive healthcare data, ensuring they meet regulatory requirements while building compliant applications.
 
 ### Expanded logging within Timescale Console
 

about/pricing-and-account-management.md

@@ -224,7 +224,7 @@ When you get $CLOUD_LONG at AWS Marketplace, the following pricing options are a
 [cloud-billing]: https://console.cloud.timescale.com/dashboard/billing/details
 [commercial-sla]: https://www.timescale.com/legal/timescale-cloud-terms-of-service
 [pricing-plans]: https://www.timescale.com/pricing
-[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
+[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan
 [production-support]: https://www.timescale.com/support
 [hipaa-compliance]: https://www.hhs.gov/hipaa/for-professionals/index.html
 [aws-pricing]: /about/:currentVersion:/pricing-and-account-management/#aws-marketplace-pricing

ai/index.md

@@ -1,6 +1,6 @@
 ---
 title: Integrate AI with Tiger Data
-excerpt: Build AI assistants with Tiger Data using pgvector, Tiger Eon, Tiger Agents, and MCP server for seamless data integration
+excerpt: Build AI Assistants with Tiger Data using pgvector, Tiger Eon, Tiger Agents, and MCP server for seamless data integration
 products: [cloud, mst, self_hosted]
 keywords: [ai, vector, pgvector, pgvectorscale, pgai, tiger-eon, tiger-agents, mcp-server]
 tags: [ai, vector, agents, assistants]
@@ -54,7 +54,7 @@ The [$MCP_LONG](/ai/:currentVersion:/mcp-server/) integrates directly with popul
 - Access comprehensive $COMPANY documentation during development
 - Use secure authentication and access control
 
-Use the $MCP_SHORT when you want to manage $COMPANY resources from your AI assistant.
+Use the $MCP_SHORT when you want to manage $COMPANY resources from your AI Assistant.
 
 
 <!-- vale Google.Headings = NO -->

getting-started/page-index/page-index.js

@@ -23,7 +23,7 @@ module.exports = [
         excerpt: "Create a Tiger service and connect to it",
       },
       {
-        title: "DevOps as code with Tiger",
+        title: "DevOps as code with Tiger Cloud",
         href: "get-started-devops-as-code",
         excerpt: "Set up secure authentication for the Tiger REST API and create your first service",
       },

integrations/cloudwatch.md

@@ -34,7 +34,7 @@ tool. You create an exporter on the [project level][projects], in the same AWS r
 <ManageDataExporter />
 
 [projects]: /use-timescale/:currentVersion:/security/members/
-[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
+[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan
 [cloudwatch]: https://aws.amazon.com/cloudwatch/
 [cloudwatch-signup]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GettingSetup.html
 

integrations/datadog.md

@@ -143,7 +143,7 @@ comprehensive list of [metrics][datadog-postgres-metrics] collected.
 [datadog-agent-restart]: https://docs.datadoghq.com/agent/configuration/agent-commands/#start-stop-and-restart-the-agent
 [projects]: /use-timescale/:currentVersion:/security/members/
 [datadog-api-key]: https://docs.datadoghq.com/account_management/api-app-keys/#add-an-api-key-or-client-token
-[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
+[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan
 [run-queries]: /getting-started/:currentVersion:/run-queries-from-console/
 [open-console]: https://console.cloud.timescale.com/dashboard/services
 [psql]: /integrations/:currentVersion:/psql/

use-timescale/backup-restore.md

@@ -1,24 +1,31 @@
 ---
-title: Back up and recover your Tiger services
-excerpt: See how and when Tiger backs up your data, making sure you always have something to fall back on in case of disaster recovery
+title: Back up and recover services
+excerpt: Tiger Cloud backs up your data, making sure you always have something to fall back on for disaster recovery
 products: [cloud]
 keywords: [backups, restore]
 tags: [recovery, failures]
 ---
 
-# Back up and recover your $SERVICE_SHORTs
+import CLIFORKS from "versionContent/_partials/_devops-cli-service-forks.mdx";
 
-$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform backups manually. What's more, with [cross-region backup][cross-region], you are protected when an entire AWS region goes down.
+# Back up and recover $SERVICE_SHORTs
 
-$CLOUD_LONG automatically creates one full backup every week, and
-incremental backups every day in the same region as your $SERVICE_SHORT. 
+$CLOUD_LONG provides comprehensive backup and recovery solutions to protect your data, including automatic daily backups, 
+cross-region protection, and point-in-time recovery.
 
-On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`. 
+## Automatic backups
+
+$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform 
+backups manually. What's more, with [cross-region backup][cross-region], you are protected when an entire AWS region goes down.
 
-Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup. This means that you always have a full backup available for the current and previous week: 
+$CLOUD_LONG automatically creates one full backup every week, and incremental backups every day in the same region as 
+your $SERVICE_SHORT. Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup. 
+This means that you always have a full backup available for the current and previous week:
 
 ![Backup in Tiger](https://assets.timescale.com/docs/images/database-backup-recovery.png)
 
+On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`. 
+
 In the event of a storage failure, a $SERVICE_SHORT automatically recovers from a backup
 to the point of failure. If the whole availability zone goes down, your $SERVICE_LONGs are recovered in a different zone. In the event of a user error, you can [create a point-in-time recovery fork][create-fork].
 
@@ -101,6 +108,7 @@ You initiate a point-in-time recovery from a same-region or cross-region backup
 1.  Confirm by clicking `Create recovery fork`.
 
     A fork of the $SERVICE_SHORT is created. The recovered $SERVICE_SHORT shows in `Services` with a label specifying which $SERVICE_SHORT it has been forked from.
+
 1.  Update the connection strings in your app
 
     Since the point-in-time recovery is done in a fork, to migrate your
@@ -120,6 +128,11 @@ You initiate a point-in-time recovery from a same-region or cross-region backup
 </Tabs>
 
 
+## Create a service fork
+
+<CLIFORKS />
+
+
 [console]: https://console.cloud.timescale.com/dashboard/services
 [ha-replicas]: /about/use-timescale/:currentVersion:/ha-replicas/
 [pricing-and-account-management]: /about/:currentVersion:/pricing-and-account-management/