move local tunnels and clean up config folder

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/local-management/index.mdx

@@ -0,0 +1,19 @@
+---
+title: Configure origin parameters
+pcx_content_type: how-to
+sidebar:
+  order: 2
+---
+
+Origin configuration parameters determine how `cloudflared` sends requests to your [public hostname](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) services.
+
+## Update origin configuration
+
+To update your origin configuration:
+
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
+2. Choose a tunnel and select **Configure**.
+3. Select the **Public Hostname** tab.
+4. Choose a route and select **Edit**.
+5. Under **Additional application settings**, modify one or more origin configuration parameters.
+6. Select **Save hostname**.

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/origin-configuration/index.mdx

@@ -1,12 +1,12 @@
 ---
 pcx_content_type: reference
-title: Origin configuration
+title: Origin configuration parameters
 sidebar:
   order: 3
 
 ---
 
-Origin configuration parameters determine how `cloudflared` proxies traffic to your origin server. You can configure these settings [in the dashboard](/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management/#update-origin-configuration) for remotely-managed tunnels, or add them to your [configuration file](/cloudflare-one/connections/connect-networks/configure-tunnels/local-management/configuration-file/#origin-configuration) for locally-managed tunnels.
+You can use the following parameters to configure how `cloudflared` proxies traffic to your origin server.
 
 ## TLS settings
 
@@ -111,7 +111,7 @@ This configures what type of proxy will be started. Valid options are:
 
 :::note
 
-For locally-managed tunnels only. 
+For locally-managed tunnels only.
 :::
 
 | Default     | UI name |
@@ -125,7 +125,7 @@ This configures the listen address for that proxy.
 
 :::note
 
-For locally-managed tunnels only. 
+For locally-managed tunnels only.
 :::
 
 | Default | UI name |

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/origin-configuration.mdx renamed to src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/origin-configuration/origin-parameters.mdx

@@ -1,156 +1,15 @@
 ---
 pcx_content_type: how-to
-title: Remotely-managed tunnel
+title: Tunnel permissions
 sidebar:
-  order: 1
+  order: 10
 ---
 
 import { TabItem, Tabs, Render } from "~/components";
 
-If you created a Cloudflare Tunnel [from the dashboard](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/), the tunnel runs as a service on your OS.
-
-## Add tunnel run parameters
-
-You can modify the Cloudflare Tunnel service with one or more [general-purpose tunnel parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/).
-
-<Tabs> <TabItem label="Linux">
-
-On Linux, Cloudflare Tunnel installs itself as a system service using `systemctl`. By default, the service will be named `cloudflared.service`. To configure your tunnel on Linux:
-
-1. Open `cloudflared.service`.
-
-   ```sh
-   sudo systemctl edit --full cloudflared.service
-   ```
-
-2. Modify the `cloudflared tunnel run` command with the desired configuration flag. For example,
-
-   ```txt null {8}
-   [Unit]
-   Description=Cloudflare Tunnel
-   After=network.target
-
-   [Service]
-   TimeoutStartSec=0
-   Type=notify
-   ExecStart=/usr/local/bin/cloudflared tunnel --loglevel debug --logfile /var/log/cloudflared/cloudflared.log run --token <TOKEN VALUE>
-   Restart=on-failure
-   RestartSec=5s
-
-   [Install]
-   WantedBy=multi-user.target
-   ```
-
-3. Restart `cloudflared.service`:
-
-   ```sh
-   sudo systemctl restart cloudflared
-   ```
-
-4. To verify the new configuration, check the service status:
-
-	```sh
-	sudo systemctl status cloudflared
-	```
-	```sh output
-	● cloudflared.service - cloudflared
-     Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; preset: enabled)
-     Active: active (running) since Wed 2024-10-09 20:02:59 UTC; 2s ago
-   Main PID: 2157 (cloudflared)
-      Tasks: 8 (limit: 1136)
-     Memory: 16.3M
-        CPU: 136ms
-     CGroup: /system.slice/cloudflared.service
-             └─2157 /usr/bin/cloudflared tunnel --loglevel debug --logfile /var/log/cloudflared/cloudflared.log run --token eyJhIjoi...
-	```
-
-</TabItem> <TabItem label="macOS">
-
-On macOS, Cloudflare Tunnel installs itself as a launch agent using `launchctl`. By default, the agent will be called `com.cloudflare.cloudflared`. To configure your tunnel on macOS:
-
-1. Stop the `cloudflared` service.
-
-   ```sh
-   sudo launchctl stop com.cloudflare.cloudflared
-   ```
-
-2. Unload the configuration file.
-
-   ```sh
-   sudo launchctl unload /Library/LaunchDaemons/com.cloudflare.cloudflared.plist
-   ```
-
-3. Open `/Library/LaunchDaemons/com.cloudflare.cloudflared.plist` in a text editor.
-
-4. Modify the `ProgramArguments` key with the desired configuration flag. For example,
-
-   ```txt
-   <plist version="1.0">
-       <dict>
-           <key>Label</key>
-           <string>com.cloudflare.cloudflared</string>
-           <key>ProgramArguments</key>
-           <array>
-               <string>/opt/homebrew/bin/cloudflared</string>
-               <string>tunnel</string>
-               <string>--logfile</string>
-               <string><PATH></string>
-               <string>--loglevel</string>
-               <string>debug</string>
-               <string>run</string>
-               <string>--token</string>
-               <string><TOKEN VALUE> </string>
-           </array>
-   ```
-
-5. Load the updated configuration file.
-
-   ```sh
-   sudo launchctl load /Library/LaunchDaemons/com.cloudflare.cloudflared.plist
-   ```
-
-6. Start the `cloudflared` service.
-
-   ```sh
-   sudo launchctl start com.cloudflare.cloudflared
-   ```
-
-</TabItem> <TabItem label="Windows">
-
-On Windows, Cloudflare Tunnel installs itself as a system service using the Registry Editor. By default, the service will be named `cloudflared`. To configure your tunnel on Windows:
-
-1. Open the Registry Editor.
-
-2. Go to **HKEY_LOCAL_MACHINE** > **SYSTEM** > **CurrentControlSet** > **Services** > **cloudflared**.
-
-3. Double-click **ImagePath**.
-
-4. Modify **Value data** with the desired configuration flag. For example,
-
-   ```txt
-   C:\Program Files (x86)\cloudflared\.\cloudflared.exe tunnel --loglevel debug --logfile <PATH> run --token <TOKEN VALUE>
-   ```
-
-![Modify cloudflared service in the Registry Editor](~/assets/images/cloudflare-one/connections/connect-apps/remote-management-windows.png)
-
-</TabItem> </Tabs>
-
-## Update origin configuration
-
-To configure how `cloudflared` sends requests to your [public hostname](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) services:
-
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
-2. Choose a tunnel and select **Configure**.
-3. Select the **Public Hostname** tab.
-4. Choose a route and select **Edit**.
-5. Under **Additional application settings**, modify one or more [origin configuration parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/origin-configuration/).
-6. Select **Save hostname**.
-
-## Tunnel permissions
-
 A remotely-managed tunnel only requires the tunnel token to run. Anyone with access to the token will be able to run the tunnel.
 
-### View the tunnel token
+## View the tunnel token
 
 To get the token for a remotely-managed tunnel:
 
@@ -178,7 +37,7 @@ Make a `GET` request to the [Cloudflare Tunnel token](/api/resources/zero_trust/
 </TabItem>
 </Tabs>
 
-### Rotate a token without service disruption
+## Rotate a token without service disruption
 
 Cloudflare recommends rotating the tunnel token at a regular cadence to reduce the risk of token compromise. You can rotate a token with minimal disruption to users as long as the tunnel is served by at least two [`cloudflared` replicas](/cloudflare-one/connections/connect-networks/deploy-tunnels/deploy-cloudflared-replicas/). To ensure service availability, we recommend performing token rotations outside of working hours or in a maintenance window.
 
@@ -272,7 +131,7 @@ To rotate a tunnel token:
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
-### Rotate a compromised token
+## Rotate a compromised token
 
 If your tunnel token is compromised, we recommend taking the following steps:
 
@@ -304,6 +163,6 @@ If your tunnel token is compromised, we recommend taking the following steps:
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 
-### Account-scoped roles
+## Account-scoped roles
 
 <Render file="tunnel/account-scoped-roles" />

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx renamed to src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-tunnel-permissions.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: concept
 title: Tunnel availability and failover
 sidebar:
-  order: 2
+  order: 4
 ---
 
 import { Details, GlossaryTooltip } from "~/components";
@@ -25,7 +25,7 @@ By design, replicas do not offer any level of traffic steering (random, hash, or
 
 To deploy multiple instances of `cloudflared`, you can create and configure one tunnel and run it on multiple hosts. If your tunnel runs as a service, only one `cloudflared` instance is allowed per host.
 
-<Details header="Via the dashboard">
+<Details header="Remotely-managed tunnels">
 
 1. To create a remotely-managed tunnel, follow the [dashboard setup guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/).
 2. On the **Tunnels** page, select your newly created tunnel. The **Connectors** section shows all of the `cloudflared` instances for that tunnel.
@@ -37,11 +37,11 @@ The new replica will appear on the **Connectors** list for the tunnel.
 
 </Details>
 
-<Details header="Via the command line">
+<Details header="Locally-managed tunnels">
 
 1. To create a locally-managed tunnel, complete Steps 1 through 5 in the [CLI setup guide](/cloudflare-one/connections/connect-networks/get-started/create-local-tunnel/).
 
-2. Next, run your newly created tunnel.
+2. Run your newly created tunnel.
 
    ```sh
    cloudflared tunnel run <NAME>
@@ -57,7 +57,7 @@ The new replica will appear on the **Connectors** list for the tunnel.
 
    This will initialize another `cloudflared` instance and generate another `connector_id`.
 
-4. Next, run `tunnel info` to show each `cloudflared` instance running your tunnel:
+4. Run `tunnel info` to show each `cloudflared` instance running your tunnel:
 
    ```sh
    cloudflared tunnel info <NAME>

src/content/docs/cloudflare-one/connections/connect-networks/deploy-tunnels/deploy-cloudflared-replicas.mdx renamed to src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: concept
 title: System requirements
 sidebar:
-  order: 3
+  order: 6
 ---
 
 import { Render, TabItem, Tabs, TunnelCalculator } from "~/components";