Fix distribution badges and tags (#1387)

* doc: Fix badges and tag * doc: Remove references to dedicated cloud
TheThingsIndustries · Nov 6, 2024 · 7cdd2d7 · 7cdd2d7
1 parent a5beaed
commit 7cdd2d7
Show file tree

Hide file tree

Showing 27 changed files with 103 additions and 156 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -80,7 +80,6 @@ If you add a section and it needs a troubleshooting page, title the troubleshoot
 The Things Stack docs cover all flavors of The Things Stack:
 
 - The Things Stack Cloud
-- The Things Stack Dedicated Cloud
 - The Things Stack AWS Launcher
 - The Things Stack Enterprise
 - The Things Stack Open Source

diff --git a/doc/content/integrations/cloud-integrations/aws-iot/_index.md b/doc/content/integrations/cloud-integrations/aws-iot/_index.md
@@ -1,7 +1,7 @@
 ---
 title: "AWS IoT"
 description: ""
-distributions: ["Cloud", "Dedicated Cloud", "Enterprise", "Sandbox"]
+distributions: ["Cloud", "Enterprise", "Sandbox"]
 aliases:
   - "/integrations/pubsub/aws-iot/"
   - "/integrations/aws-iot/default/"

diff --git a/doc/content/integrations/cloud-integrations/azure-iot-central/_index.md b/doc/content/integrations/cloud-integrations/azure-iot-central/_index.md
@@ -1,7 +1,7 @@
 ---
 title: "Azure IoT Central"
 description: ""
-distributions: ["Cloud", "Dedicated Cloud", "Enterprise", "Sandbox"]
+distributions: ["Cloud", "Enterprise", "Sandbox"]
 aliases: ["/azure-iot-central"]
 ---
 

diff --git a/doc/content/integrations/cloud-integrations/azure-iot-hub/_index.md b/doc/content/integrations/cloud-integrations/azure-iot-hub/_index.md
@@ -1,7 +1,7 @@
 ---
 title: "Azure IoT Hub"
 description: ""
-distributions: ["Cloud", "Dedicated Cloud", "Enterprise", "Sandbox"]
+distributions: ["Cloud", "Enterprise", "Sandbox"]
 ---
 
 This guide will help you setup the [Azure IoT Hub](https://azure.microsoft.com/en-us/services/iot-hub/) integration.

diff --git a/doc/content/integrations/cloud-integrations/daizy/index.md b/doc/content/integrations/cloud-integrations/daizy/index.md
@@ -1,7 +1,7 @@
 ---
 title: "Daizy"
 description: ""
-distributions: ["Cloud", "Dedicated Cloud", "Enterprise", "Sandbox"]
+distributions: ["Cloud", "Enterprise", "Sandbox"]
 ---
 
 Use [Daizy](https://daizy.io) to rapidly build, deploy and scale Internet of Things applications and stay in control of your data.

diff --git a/doc/content/integrations/storage/_index.md b/doc/content/integrations/storage/_index.md
@@ -3,7 +3,7 @@ title: Storage Integration
 description: ""
 summary: Persistent storage for upstream messages.
 distributions:
-  ["Cloud", "Dedicated Cloud", "Enterprise", "AWS Launcher", "Sandbox"]
+  ["Cloud", "Enterprise", "AWS Launcher", "Sandbox"]
 ---
 
 The Storage Integration allows storing received upstream messages in a persistent database, and retrieving them at a later time.

diff --git a/doc/content/reference/configuration/application-server.md b/doc/content/reference/configuration/application-server.md
@@ -99,7 +99,7 @@ Application Server can use Javascript payload formatters to decode uplink and en
 
 ## Storage Integration Options
 
-{{< distributions "Enterprise" "AWS Launcher" "Dedicated Cloud" >}} The Storage Integration requires a database for storing upstream messages.
+{{< distributions "Enterprise" "AWS Launcher" >}} The Storage Integration requires a database for storing upstream messages.
 
 - `as.packages.storage.provider`: Database backend to use. Currently, only `postgres` is supported.
 

diff --git a/doc/content/reference/configuration/the-things-stack.md b/doc/content/reference/configuration/the-things-stack.md
@@ -368,7 +368,7 @@ Tenants can have custom configuration, such as custom branding or custom user re
 
 ## Resource Limiting
 
-{{< distributions "Dedicated Cloud" "Enterprise" "AWS Launcher" >}}  {{% tts %}} supports configuring maximum limits for active resources (e.g. number of active application data-plane MQTT connections). Resource limiting configuration can only be set from the configuration file. See [Resource Limiting]({{< ref "/reference/resource-limiting" >}}) for more details.
+{{< distributions "Enterprise" "AWS Launcher" >}}  {{% tts %}} supports configuring maximum limits for active resources (e.g. number of active application data-plane MQTT connections). Resource limiting configuration can only be set from the configuration file. See [Resource Limiting]({{< ref "/reference/resource-limiting" >}}) for more details.
 
 ## Version Check
 

diff --git a/doc/content/reference/data-retention/_index.md b/doc/content/reference/data-retention/_index.md
@@ -12,23 +12,23 @@ This reference contains information about what access administrators and users h
 
 To understand how data is secured in {{% tts %}} it is necessary to understand some important roles:
 
-**Infrastructure Owners**: Those with access to the hardware {{% tts %}} runs on. For {{% tts %}} Cloud, Dedicated Cloud and {{% ttss %}}, this is The Things Industries. {{% tts %}} Enterprise and Open Source deployments are managed by the customer and user respectively; The Things Industries does not have any infrastructural access. Technically, **Infrastructure Owners** have access to all data stored in databases or persistent volumes. In practice, The Things Industries uses this direct data access to {{% tts %}} Cloud or {{% ttss %}} deployments only for backups.
+**Infrastructure Owners**: Those with access to the hardware {{% tts %}} runs on. For {{% tts %}} Cloud and {{% ttss %}}, this is The Things Industries. {{% tts %}} Enterprise and Open Source deployments are managed by the customer and user respectively; The Things Industries does not have any infrastructural access. Technically, **Infrastructure Owners** have access to all data stored in databases or persistent volumes. In practice, The Things Industries uses this direct data access to {{% tts %}} Cloud or {{% ttss %}} deployments only for backups.
 
 **Network Administrators**: Users with administrative access in a tenant. **Network Administrators** have access to all entities in a tenant, including device secrets. In multi-tenant environments, tenants are completely isolated, and **Network Administrators** of one tenant have **no access** to other tenants.
 
 **Users and Organizations**: Users without administrative access, and organizations, can access entities which they have [collaborator rights]({{< ref "/the-things-stack/management/user-management" >}}) over.
 
 **Support Engineers**: The Things Industries support engineers do **not** have infrastructural access to any {{% tts %}} deployments. They must be [granted access]({{< ref "/the-things-stack/management/user-management" >}}) by the customer.
 
-## {{% tts %}} Cloud and Dedicated Cloud
+## {{% tts %}} Cloud
 
-The following information applies to {{% tts %}} deployments hosted by The Things Industries, specifically {{% tts %}} Cloud and Dedicated Cloud.
+The following information applies to {{% tts %}} deployments hosted by The Things Industries, specifically {{% tts %}} Cloud.
 
 {{% tts %}} deployments hosted on customer hardware, specifically {{% tts %}} Enterprise, are completely managed by the customer and can be configured to meet more specific data privacy requirements.
 
 ### Persisted Data
 
-On {{% tts %}} Cloud and Dedicated Cloud, the Network Server stores
+On {{% tts %}} Cloud the Network Server stores
 
 - Recent uplinks as part of the MAC state, in a Redis database
 

diff --git a/doc/content/the-things-stack/cloud/billing-and-subscription-management/_index.md b/doc/content/the-things-stack/cloud/billing-and-subscription-management/_index.md
@@ -35,7 +35,7 @@ To sign up for any of the above mentioned plans, just click on the button on the
 
 If you are not looking for a cloud but for an enterprise solution, make sure to check out [self-hosted {{% tts %}} options](https://www.thethingsindustries.com/deployment/).
 
-{{< note >}} Some deployments (e.g. **{{% tts %}} Dedicated Cloud**) and some support plans (e.g. **Consulting**) are not available for purchase through the platform. Instead, you need to [contact The Things Industries](mailto:[email protected]) to proceed. {{</ note >}}
+{{< note >}} Some deployments and some support plans (e.g. **Consulting**) are not available for purchase through the platform. Instead, you need to [contact The Things Industries](mailto:[email protected]) to proceed. {{</ note >}}
 
 ## Creating Your Network
 

diff --git a/doc/content/the-things-stack/concepts/server-addresses/_index.md b/doc/content/the-things-stack/concepts/server-addresses/_index.md
@@ -24,7 +24,7 @@ You can update the examples below with your tenant ID and cluster ID by filling
 
 ## Deployments
 
-**Cloud and Dedicated Cloud**: See [Cloud Addresses]({{< ref "/the-things-stack/cloud/addresses" >}}).
+**Cloud**: See [Cloud Addresses]({{< ref "/the-things-stack/cloud/addresses" >}}).
 
 **AWS Launcher**: This is the domain you specify in your [CloudFormation configuration]({{< ref "the-things-stack/host/aws/ami/deployment-guide#step-2-configure-the-deployment" >}}).
 

diff --git a/doc/content/the-things-stack/packet-broker/configure/_index.md b/doc/content/the-things-stack/packet-broker/configure/_index.md
@@ -4,7 +4,6 @@ description: ""
 weight: 2
 distributions:
   - Cloud
-  - Dedicated Cloud
   - Enterprise
   - Open Source
 aliases:
@@ -27,7 +26,6 @@ To see which routing policies are configured by default for all deployments, see
 1. Understand how Packet Broker works and what routing policies are. [Learn about Packet Broker]({{< relref "../" >}}).
 2. {{% tts %}} connected to Packet Broker.
   - {{< distributions "Cloud" >}} **{{% tts %}} Cloud** is already connected to Packet Broker.
-  - {{< distributions "Dedicated Cloud" >}} **{{% tts %}} Dedicated Cloud** can be connected on request. Please [contact The Things Industries support](mailto:[email protected]).
   - {{< distributions "Enterprise" "Open Source" >}} **{{% tts %}} Enterprise** and **Open Source**: see [Connect]({{< relref "connect" >}}).
 3. An admin account for the {{% tts %}} deployment. All Packet Broker configuration requires administrative access.
 
@@ -133,7 +131,7 @@ To register or update your existing tenant registration:
 ttn-lw-cli packetbroker register --listed
 ```
 
-This updates the registration with Packet Broker based on your {{% tts %}} environment. When using {{% tts %}} Cloud or Dedicated Cloud, the registration is based on your subscription. When using {{% tts %}} Enterprise or Open Source, the registration is based on [your configuration]({{< relref "configure" >}}).
+This updates the registration with Packet Broker based on your {{% tts %}} environment. When using {{% tts %}} Cloud, the registration is based on your subscription. When using {{% tts %}} Enterprise or Open Source, the registration is based on [your configuration]({{< relref "configure" >}}).
 
 With `--listed`, you make your network publicly listed so it can be found by other network administrators. This flag is optional.
 

diff --git a/doc/content/the-things-stack/packet-broker/configure/gateway-visibilities.md b/doc/content/the-things-stack/packet-broker/configure/gateway-visibilities.md
@@ -4,7 +4,6 @@ description: ""
 weight: 2
 distributions:
   - Cloud
-  - Dedicated Cloud
   - Enterprise
   - Open Source
 new_in_version: 3.15.1

diff --git a/doc/content/the-things-stack/packet-broker/configure/routing-policies.md b/doc/content/the-things-stack/packet-broker/configure/routing-policies.md
@@ -4,7 +4,6 @@ description: ""
 weight: 1
 distributions:
   - Cloud
-  - Dedicated Cloud
   - Enterprise
   - Open Source
 aliases: [/getting-started/packet-broker/configure/routing-policies]

diff --git a/doc/data/distributions.yml b/doc/data/distributions.yml
@@ -3,11 +3,6 @@ Cloud:
   color: "#0032B4"
   icon: "img/tts_frames/frame_cloud.svg"
   weight: 1
-Dedicated Cloud:
-  name: "Dedicated Cloud"
-  color: "#D356FF"
-  icon: "img/tts_frames/frame_dedicated_cloud.svg"
-  weight: 2
 Sandbox:
   name: "Sandbox"
   color: "#F304FF"

diff --git a/doc/data/glossary.yml b/doc/data/glossary.yml
@@ -370,9 +370,6 @@
 - term: The Things Stack AWS Launcher
   description: AWS marketplace makes it easy to deploy in one click on new or existing EC2 cluster. Integrates effortlessly with AWS IOT, so you can keep using tools you're already familiar with.
 
-- term: The Things Stack Dedicated Cloud
-  description: All the benefits of The Things Stack Cloud on a dedicated cluster.
-
 - term: The Things Stack Enterprise (TTSE)
   description: Install the network components on your own hardware, with professional support from The Things Industries.
 

diff --git a/doc/static/img/tts_frames/frame_aws.svg b/doc/static/img/tts_frames/frame_aws.svg
diff --git a/doc/static/img/tts_frames/frame_cloud.svg b/doc/static/img/tts_frames/frame_cloud.svg