docs: IA reorganization (#5838)

* docs: IA reorganization * docs: Updates * docs: Updates * docs: Fix links * docs: Updates * docs: Fix a typo * docs: Fix client agent topic * docs: Update Client Agent nav * docs: Fix conflict * docs: Fix a typo in Client Agent docs (#5853) * docs: Fix client agent topic * docs: Updates * docs: Updates * docs: Updates * docs: Updates * docs: Fixes get started and operations links * docs: Update nav * docs: Partials * docs: Unix partials * docs: Worker partials * docs: Updates * docs: Update workers and targets * docs: Updates * docs: Updates * docs: Fixes link * docs: Updates after sync review * docs: Updates from review feedback * docs: Move worker filter examples * docs: Fix links * docs: Updates for filters based on working session * docs: Fixes broken links * docs: Add links to other filter topics * docs: Update list intro * docs: Adds link * docs: Fixes redirects * docs: Fixes redirects * docs: Deleted mysql page from TOC * docs: Add versioned redirect * docs: Adds versioned redirects * docs: Adds versioned redirects * docs: Update redirects * docs: Update redirects * docs: Redirect fixes * docs: Update redirect format * docs: Fix a typo * docs: Fixes redirects * docs: Fixes redirect * docs: Adds links out to client agent troubleshooting * uses /etc/boundary.d/ as recommended installation directory (#6003) * docs: Updates legacy io links * docs: Fixes redirects * docs: Fix redirect * docs: Restoring deleted file --------- Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
2025-09-03 15:45:38 -04:00
1 parent 21fce7c5eb
commit 5ce6515156
@@ -30,7 +30,7 @@ boundary connect -target-id ttcp_0987654321

 For the purpose of this guide, both of these targets accomplish the same goal,
 however they have different purposes. Refer to the
-[domain](/boundary/docs/concepts/domain-model/index) documentation for more information.
+[domain model](/boundary/docs/domain-model/) documentation for more information.

 For the rest of this guide, assume the default is used.

@@ -82,7 +82,7 @@ These are written as `boundary connect <subcommand>` and are supported for the f
 - RDP
 - SSH

-Refer to the [Connect helpers](/boundary/docs/concepts/connection-workflows/connect-helpers) documentation for more information.
+Refer to the [Connect helpers](/boundary/docs/targets/connections/connect-helpers) documentation for more information.

 ## Built-in vs. exec

@@ -93,7 +93,7 @@ tool, allowing you to wrap Boundary TCP sessions in your preferred
 client. You can use this flag to create an authenticated proxy to almost
 anything.

-Refer to the [Exec flag](/boundary/docs/concepts/connection-workflows/exec-flag) documentation for more information.
+Refer to the [Exec flag](/boundary/docs/targets/connections/exec-flag) documentation for more information.

 ## SSH ProxyCommand

@@ -101,7 +101,7 @@ SSH `ProxyCommand` lets you proxy an SSH connection to a target according to a c
 It can help simplify common developer and operator workflows.
 You can configure the file to connect to the target ID or the target domain.

-Refer to the [SSH ProxyCommand](/boundary/docs/concepts/connection-workflows/workflow-ssh-proxycommand) documentation for more information.
+Refer to the [SSH ProxyCommand](/boundary/docs/targets/connections/workflow-ssh-proxycommand) documentation for more information.

 ## Desktop client

@@ -124,5 +124,5 @@ proxy details.
 ## Next steps

 See our [basic administration
-workflows](/boundary/tutorials/oss-administration)
+workflow](/boundary/tutorials/community-administration) tutorials
 for in depth discussion on managing scopes, targets, identities, and sessions.
@@ -10,9 +10,13 @@ description: >-
 Dev mode is a method for getting started with Boundary quickly for testing and
 learning purposes. As the name implies, dev mode is not a production
 installation method, and provides a way to get Boundary running with a Postgres
-database easily. Do not use dev mode in a production environment, see the
-[Production Installation](/boundary/docs/oss/installing/high-availability) section for
-production-ready deployment methods.
+database easily.
+
+Do not use dev mode in a production environment, refer to the following sections for production-ready deployment methods:
+
+- [Deploy Boundary in a self-managed environment](/boundary/docs/deploy/self-managed)
+- [Deploy HCP Boundary](/boundary/docs/hcp/get-started/deploy-and-login)
+- [Terraform patterns for Boundary](/boundary/docs/deploy/terraform-patterns)

 Dev mode brings up a fully-functioning instance of Boundary, including:

@@ -25,22 +29,22 @@ across dev mode restarts. Along with these external components, dev mode also
 creates several resources within Boundary to make it easier and faster to
 connect to your first target:

-1. An org [scope](/boundary/docs/concepts/domain-model/scopes) and a project scope with a
+1. An org [scope](/boundary/docs/domain-model/scopes) and a project scope with a
   default ID of `o_1234567890` and `p_1234567890` respectively.
-1. A password [auth method](/boundary/docs/concepts/domain-model/auth-methods) with a
+1. A password [auth method](/boundary/docs/domain-model/auth-methods) with a
   default auth method ID of `ampw_1234567890`.
-1. An OIDC [auth method](/boundary/docs/concepts/domain-model/auth-methods) with a
+1. An OIDC [auth method](/boundary/docs/domain-model/auth-methods) with a
   default auth method ID of `amoidc_1234567890`.
 1. An admin user with login name `admin` and password `password`.
 1. An unprivileged user with login name `user` and password `password`.
-1. A static [host catalog](/boundary/docs/concepts/domain-model/host-catalogs) with a
+1. A static [host catalog](/boundary/docs/domain-model/host-catalogs) with a
   default ID of `hcst_1234567890`.
-1. A static [host](/boundary/docs/concepts/domain-model/hosts) and [host
-   set](/boundary/docs/concepts/domain-model/host-sets) with default ID's of
+1. A static [host](/boundary/docs/domain-model/hosts) and [host
+   set](/boundary/docs/domain-model/host-sets) with default ID's of
   `hst_1234567890` and `hsst_1234567890` respectively.
-1. A TCP [target](/boundary/docs/concepts/domain-model/targets) with a default ID of
+1. A TCP [target](/boundary/docs/domain-model/targets) with a default ID of
   `ttcp_1234567890`, directly set-up with an address and port.
-1. A TCP [target](/boundary/docs/concepts/domain-model/targets) with a default ID of
+1. A TCP [target](/boundary/docs/domain-model/targets) with a default ID of
   `ttcp_0987654321` using the previously mentioned static host set.

 The default ID suffixes can be overwritten or randomly generated, and there are
@@ -68,12 +68,10 @@ name and password:


 <Tab heading="Desktop Client">
-<p>

-
-To authenticate using the Boundary desktop client, launch Boundary desktop client
-and connect to boundary to using [http://127.0.0.1:9200](http://127.0.0.1:9200)
-and enter the login name and password:
+To authenticate using the Boundary desktop client, launch the Boundary desktop client
+and connect to Boundary using [http://127.0.0.1:9200](http://127.0.0.1:9200),
+then enter the login name and password:

 <video
  muted
@@ -88,7 +86,6 @@ and enter the login name and password:
  />
 </video>

-</p>
 </Tab>


@@ -117,5 +114,5 @@ the Boundary server does not use TLS in development mode.
 ## Next steps

 See [connecting to your first
-target](/boundary/docs/oss/installing/connect-to-dev-target) for how to use Boundary to
+target](/boundary/docs/getting-started/dev-mode/connect-to-dev-target) for how to use Boundary to
 run your first SSH session.