website: Flesh out docs split.

website: Copy files during build.

website: Allow for mixed env builds.

website: Reduce build size.

website: Expose build.

website: Add build memory debugging.

WIP: Disable broken links check to compare memory usage.

website: Update deps.

website: Clean up API paths.

website: Flesh out 3.8 fixes.

Format.

website: Update ignore paths.

Website: Clean up integrations build.

website: Fix paths.

website: Optimize remark.

website: Update deps.

website: Format.

website: Remove linking.

website: Fix paths.

wip: Attempt API only build.

Prep.

Migrate render to runtime. Tidy sidebar.

Clean up templates.

docs: Move directory. WIP

docs: Flesh out split.

website: Fix issue where routes have collisions.

docs/topics/add-secure-apps/outposts/embedded/embedded.mdx

@@ -0,0 +1,47 @@
+---
+title: Embedded Outpost
+---
+
+Starting with 2021.8.1, authentik comes with an embedded outpost. This has been added to simplify deployment for users using the Proxy provider.
+
+The embedded outpost runs in the main `server` container, and is managed by authentik itself. The embedded outpost authenticates itself via the secret key.
+
+You can access the embedded outpost on the same ports as authentik itself, 9000 and 9443.
+
+If the embedded outpost doesn't make sense for your deployment, you can simply ignore it.
+
+### Configuration
+
+Since authentik doesn't know it's own "primary" URL, there might be some configuration required.
+
+By default, when opening the admin dashboard on a fresh install, authentik will automatically configure the outpost to use the same URL as was used to access authentik.
+
+If this isn't correct, or needs to be changed, click the edit button on the right of the outpost, and set the value of `authentik_host` to the URL you want to login with.
+Make sure to set it to full URL, only configuring a hostname or FQDN will not work.
+
+Additionally, most of the other configuration options can be used as with any other outpost, except from items which are marked as "non-embedded"
+
+import Configuration from "../_config.md";
+
+<Configuration />
+
+### Routing
+
+Routing is handled like this:
+
+1. Paths starting with `/static`, `/media` and `/help` return packaged CSS/JS files, and user-uploaded media files.
+2. Paths starting with `/outpost.goauthentik.io` are sent to the embedded outpost.
+3. Any hosts configured in the providers assigned to the embedded outpost are sent to the outpost.
+4. Everything remaining is sent to the authentik backend server.
+
+### Differences
+
+There are a few more differences between managed outposts and the embedded outpost, mainly due to the fact that authentik can't fully manage the containers.
+
+1. (Docker-only) No automatic traefik labels are added to the server container.
+
+    When you deploy a managed outpost on docker, the container has several labels to automatically configure traefik. This is not done for the embedded outpost.
+
+2. (Kubernetes-only) An additional service is created.
+
+    Since authentik does not know what the normal authentik Service is called, another one is created with a common set of labels that is always set.