fix(influxdb3): Get started fixes

Author: jstirnaman

content/influxdb3/enterprise/admin/license.md

@@ -101,7 +101,7 @@ The license file is a JWT file that contains the license information.
 > use one of the methods to [skip the email prompt](#skip-the-email-prompt). 
 > This ensures that the container can generate the license file after you
 > verify your email address.
-> See the [Docker Compose example](?t=Docker+compose#activate-a-trial-or-home-license-with-docker).
+> See the [Docker Compose example](?t=Docker+compose#start-with-license-email-and-compose).
 
 #### Skip the email prompt
 
@@ -186,7 +186,7 @@ existing license if it's still valid.
 {{% code-tabs %}}
 [influxdb3 options](#)
 [Environment variables](#)
-[Docker compose](#example-activate-trial-or-home-with-compose)
+[Docker compose](#start-with-license-email-and-compose)
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 <!------------------------ BEGIN INFLUXDB3 CLI OPTIONS ------------------------>
@@ -215,6 +215,7 @@ influxdb3 serve \
 {{% /code-tab-content %}}
 {{% code-tab-content %}}
 <!------------------------ BEGIN DOCKER COMPOSE ------------------------>
+{{% code-placeholders "${EMAIL_ADDRESS}" %}}
 ```yaml
 # compose.yaml
 name: data-crunching-stack
@@ -235,7 +236,8 @@ services:
       - --object-store=file
       - --data-dir=/var/lib/influxdb3
       - --plugin-dir=/var/lib/influxdb3/plugins
-      - --license-email=INFLUXDB3_LICENSE_EMAIL
+    environment:
+      - INFLUXDB3_LICENSE_EMAIL=${EMAIL_ADDRESS}
     volumes:
       - type: bind 
         source: ~/.influxdb3/data
@@ -244,6 +246,9 @@ services:
         source: ~/.influxdb3/plugins
         target: /var/lib/influxdb3/plugins
 ```
+{{% /code-placeholders %}}
+Replace {{% code-placeholder-key %}}`${EMAIL_ADDRESS}`{{% /code-placeholder-key %}} with your email address
+or a variable from your Compose `.env` file.
 <!------------------------- END DOCKER COMPOSE ------------------------->
 {{% /code-tab-content %}}
 {{< /code-tabs-wrapper >}}

content/influxdb3/enterprise/install/multi-server.md

@@ -24,10 +24,7 @@ object store.
 - [Connect to your object store](#connect-to-your-object-store)
 - [Server modes](#server-modes)
   - [Server mode examples](#server-mode-examples)
-    - [Configure a node to only handle write requests](#configure-a-node-to-only-handle-write-requests)
-    - [Configure a node to only run the Compactor](#configure-a-node-to-only-run-the-compactor)
-    - [Configure a handle query requests and run the processing engine](#configure-a-handle-query-requests-and-run-the-processing-engine)
-- [InfluxDB 3 Enterprise cluster configuration examples](#influxdb-3-enterprise-cluster-configuration-examples)
+- [Cluster configuration examples](#cluster-configuration-examples)
   - [High availability cluster](#high-availability-cluster)
   - [High availability with a dedicated Compactor](#high-availability-with-a-dedicated-compactor)
   - [High availability with read replicas and a dedicated Compactor](#high-availability-with-read-replicas-and-a-dedicated-compactor)
@@ -184,8 +181,7 @@ influxdb3 serve \
   --mode query,process
 ```
 
-
-## {{% product-name %}} cluster configuration examples
+## Cluster configuration examples
 
 <!-- Placeholder for links -->
 

content/influxdb3/enterprise/reference/config-options.md

@@ -320,7 +320,6 @@ The server processes all requests without requiring tokens or authentication.
 Optionally disable authz by passing in a comma separated list of resources. 
 Valid values are `health`, `ping`, and `metrics`.
 
-
 ---
 
 ### AWS

content/shared/influxdb3-get-started/processing-engine.md

@@ -89,15 +89,13 @@ def process_writes(influxdb3_local, table_batches, args=None):
         influxdb3_local.info("arg1: " + args["arg1"])
 
     # here we're using arguments provided at the time the trigger was set up 
-    # to feed into paramters that we'll put into a query
+    # to feed into parameters that we'll put into a query
     query_params = {"room": "Kitchen"}
-    # here's an example of executing a parameterized query. Only SQL is supported. 
-    # It will query the database that the trigger is attached to by default. We'll 
-    # soon have support for querying other DBs.
-    query_result = influxdb3_local.query("SELECT * FROM home where room = '$host'", query_params)
-    # the result is a list of Dict that have the column name as key and value as 
-    # value. If you run the WAL test plugin with your plugin against a DB that 
-    # you've written data into, you'll be able to see some results
+    # The following example shows how to execute a parameterized query. Only SQL is supported. 
+    # It queries the database that the trigger is configured for.
+    query_result = influxdb3_local.query("SELECT * FROM home where room = '$room'", query_params)
+    # The result is a list of Dict that have the column name as key and value as 
+    # value.
     influxdb3_local.info("query result: " + str(query_result))
 
     # this is the data that is sent when the WAL is flushed of writes the server 
@@ -180,18 +178,7 @@ Replace the following:
 - {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}: the {{% token-link "admin" %}} for your {{% product-name %}} server
 - {{% code-placeholder-key %}}`PLUGIN_FILENAME`{{% /code-placeholder-key %}}: the name of the plugin file to test
 
-The command runs the plugin code with the test data, yields the data to the
-plugin code, and then responds with the plugin result.
-You can quickly see how the plugin behaves, what data it would have written to
-the database, and any errors.
-You can then edit your Python code in the plugins directory, and rerun the test.
-The server reloads the file for every request to the `test` API.
-
-With the plugin code inside the server plugin directory, and a successful test,
-you're ready to create a trigger for your server to run the plugin.
-
-##### Example: Test and run a plugin
-
+### Example: Test a plugin
 <!-- pytest.mark.skip -->
 ```bash
 # Test a plugin
@@ -207,6 +194,13 @@ influxdb3 test wal_plugin \
   test.py
 ```
 
+The command runs the plugin code with the test data, yields the data to the
+plugin code, and then responds with the plugin result.
+You can quickly see how the plugin behaves, what data it would have written to
+the database, and any errors.
+You can then edit your Python code in the plugins directory, and rerun the test.
+The server reloads the file for every request to the `test` API.
+
 For more information, see [`influxdb3 test wal_plugin`](/influxdb3/version/reference/cli/influxdb3/test/wal_plugin/)
 or run `influxdb3 test wal_plugin -h`.
 

content/shared/influxdb3-get-started/setup.md

@@ -1,10 +1,10 @@
 <!-- TOC -->
 - [Prerequisites](#prerequisites)
 - [Start InfluxDB](#start-influxdb)
-- [Configure for your object store](#configure-for-your-object-store)
   - [Object store examples](#object-store-examples)
 {{% show-in "enterprise" %}}
 - [Set up licensing](#set-up-licensing)
+  - [Available license types](#available-license-types)
 {{% /show-in %}}
 - [Set up authorization](#set-up-authorization)
   - [Create an operator token](#create-an-operator-token)
@@ -18,8 +18,8 @@ To get started, you'll need:
 
 - **{{% product-name %}}**: [Install and verify the latest version](/influxdb3/version/install/) on your system.
 - If you want to persist data, have access to one of the following:
+  - A directory on your local disk where you can persist data (used by examples in this guide)
   - S3-compatible object store and credentials
-  - A directory on your local disk where you can persist data
 
 ## Start InfluxDB
 
@@ -52,13 +52,6 @@ Provide the following:
   - `google`: Google Cloud Storage
   - `azure`: Azure Blob Storage
 
-  > [!Note]  
-  > Examples in this getting started guide use the `file` object
-  > store to persist data to your local disk.
-
-The following examples show how to start {{% product-name %}} with different
-object store configurations.
-
 > [!Note]
 > #### Diskless architecture
 >
@@ -97,7 +90,7 @@ influxdb3 serve \
 ```
 {{% /show-in %}}
 
-### {{% product-name %}} store examples
+### Object store examples
 
 {{< expand-wrapper >}}
 {{% expand "File system object store" %}}
@@ -198,10 +191,12 @@ docker run -it \
          - --object-store=file
          - --data-dir=/var/lib/influxdb3
          - --plugins-dir=/var/lib/influxdb3-plugins
-         - --license-email=EMAIL_ADDRESS
+       environment:
+         - INFLUXDB3_LICENSE_EMAIL=EMAIL_ADDRESS
    ```
    _Replace `EMAIL_ADDRESS` with your email address to bypass the email prompt
-   when generating a trial or at-home license._
+   when generating a trial or at-home license. For more information, see [Manage your
+   {{% product-name %}} license](/influxdb3/version/admin/license/)_.
 {{% /show-in %}}
 {{% show-in "core" %}}
 1. Open `compose.yaml` for editing and add a `services` entry for {{% product-name %}}--for example:
@@ -360,7 +355,6 @@ influxdb3 serve --help
 ## Set up licensing
 
 When you first start a new instance, {{% product-name %}} prompts you to select a
-
 license type.
 
 InfluxDB 3 Enterprise licenses:
@@ -369,7 +363,7 @@ InfluxDB 3 Enterprise licenses:
 - **Apply per cluster**, with limits based primarily on CPU cores.
 - **Vary by license type**, each offering different capabilities and restrictions.
 
-### Available license types:
+### Available license types
 
 - **Trial**: 30-day trial license with full access to InfluxDB 3 Enterprise capabilities.
 - **At-Home**: For at-home hobbyist use with limited access to InfluxDB 3 Enterprise capabilities.
@@ -378,40 +372,14 @@ InfluxDB 3 Enterprise licenses:
 > [!Important]
 > #### Trial and at-home licenses with Docker
 >
-> To generate a trial or home license for InfluxDB 3 in Docker, the first time
-> you start a new instance, provide your email address with the
-> `--license-email` option or the
-> `INFLUXDB3_LICENSE_EMAIL` environment variable to bypass the licensing
-> email prompt--for example, in a Docker Compose file:
->
-> {{% code-placeholders "EMAIL_ADDRESS" %}}
-> ```yaml
-> # compose.yaml
-> services:
->   influxdb3-{{< product-key >}}:
->     container_name: influxdb3-{{< product-key >}}
->     image: influxdb:3-{{< product-key >}}
->     ports:
->       - 8181:8181
->     command:
->       - influxdb3
->       - serve
->       - --node-id=node0
->       - --object-store=file
->       - --data-dir=/var/lib/influxdb3
->       - --plugins-dir=/var/lib/influxdb3-plugins
-      environment:
->       - INFLUXDB3_LICENSE_EMAIL=${EMAIL_ADDRESS}
-> ```
-> {{% /code-placeholders %}}
-> {{% code-placeholder-key %}}`EMAIL_ADDRESS`{{% /code-placeholder-key %}} is
-> the email you want to associate with the license. This example shows how
-> to reference a variable in your `.env` file.
+> To generate the trial or home license in Docker, bypass the email prompt.
+> The first time you start a new instance, provide your email address with the
+> `--license-email` option or the `INFLUXDB3_LICENSE_EMAIL` environment variable.
 >
-> _Currently, if you use the prompt to enter your email address, a bug may
+> _Currently, if you use Docker and enter your email address in the prompt, a bug may
 > prevent the container from generating the license ._
 >
-> For more information, see [Manage your InfluxDB 3 Enterprise license](/influxdb3/enterprise/admin/license/).
+> For more information, see [the Docker Compose example](/influxdb3/enterprise/admin/license/?t=Docker+compose#start-the-server-with-your-license-email).
 {{% /show-in %}}
 
 > [!Tip]

content/shared/influxdb3-get-started/write.md

@@ -152,7 +152,7 @@ Include the following:
 - `--database` option that identifies the target database
 - `--token` option that specifies the token to use _(unless the `INFLUXDB3_AUTH_TOKEN`
   environment variable is already set)_
-- Quoted line protocol data via standard input (stdin) or a file
+- Quoted line protocol data via standard input (stdin)
 
 {{% code-placeholders "DATABASE_NAME|AUTH_TOKEN" %}}
 ```bash