add client redirects for old quick start watt link

Signed-off-by: Leonardo Rossi <leonardo.rossi@gmail.com>

Author: leorossi

docs/reference/runtime/_shared-configuration.md

@@ -384,6 +384,34 @@ This configures the Platformatic Runtime Prometheus server. The Prometheus serve
 - **`plugins`** (array of `string`): A list of Fastify plugin to add to the Prometheus server.
 - **`applicationLabel`** (`string`, default: `'applicationId'`): The label name to use for the application identifier in metrics (e.g., `'applicationId'`, `'serviceId'`, or any custom label name).
 - **`timeout`** (`number`, default: `10000`): The timeout to wait for each worker metrics before skipping it.
+<<<<<<< HEAD
+=======
+- **`otlpExporter`** (`object`): Optional configuration for exporting Prometheus metrics to an OpenTelemetry Protocol (OTLP) endpoint. This enables pushing metrics to OTLP-compatible collectors like OpenTelemetry Collector, Grafana Cloud, or other observability platforms. The object supports the following settings:
+  - **`enabled`** (`boolean` or `string`): Enable or disable OTLP metrics export. Default: `true` if endpoint is configured.
+  - **`endpoint`** (**required**, `string`): OTLP endpoint URL for metrics (e.g., `http://localhost:4318/v1/metrics`).
+  - **`interval`** (`number` or `string`): Interval in milliseconds between metric pushes. Default: `60000` (60 seconds).
+  - **`headers`** (`object`): Additional HTTP headers for authentication or custom metadata. Common use cases include API keys or authentication tokens.
+  - **`serviceName`** (`string`): Service name for OTLP resource attributes. Defaults to the application ID.
+  - **`serviceVersion`** (`string`): Service version for OTLP resource attributes. Optional.
+
+```json title="Example OTLP Metrics Configuration"
+{
+  "metrics": {
+    "enabled": true,
+    "port": 9090,
+    "otlpExporter": {
+      "endpoint": "http://otel-collector:4318/v1/metrics",
+      "interval": 30000,
+      "headers": {
+        "x-api-key": "{OTLP_API_KEY}"
+      },
+      "serviceName": "my-platformatic-app",
+      "serviceVersion": "1.0.0"
+    }
+  }
+}
+```
+>>>>>>> 56907777 (add client redirects for old quick start watt link)
 
 If the `metrics` object is not provided, the Prometheus server will not be started.
 

docs/reference/runtime/programmatic.md

@@ -54,4 +54,74 @@ import { loadConfiguration } from '@platformatic/runtime'
 const config = await loadConfiguration('/path/to/platformatic.config.json')
 ```
 
+## Adding and Removing applications at runtime
+
+The Runtime object provides methods to dynamically add and remove applications during runtime execution.
+
+### API Documentation
+
+### `runtime.addApplications(applications, start = false)`
+
+Dynamically adds new applications to a running runtime instance. This allows you to register applications after the runtime has been initialized.
+
+If `start` is `true`, then the new application will immediately be started in parallel. Defaults to `false`.
+
+**Important**: Application objects passed in the `applications` argument should always be processed via `prepareApplication` first to ensure proper options normalization.
+
+```js
+import { create, prepareApplication } from '@platformatic/runtime'
+
+const app = await create('path/to/platformatic.runtime.json')
+// const app = await create('path/to/watt.json')
+await app.start()
+
+// Prepare and add new applications dynamically
+const newApplications = [
+  await prepareApplication(app.getRuntimeConfig(true), { id: 'my-new-service', path: './new-service' })
+]
+
+await app.addApplications(newApplications, true) // true to start immediately
+```
+
+#### `runtime.removeApplications(applications, silent = false)`
+
+Dynamically removes applications from the runtime. This will stop the applications and clean up their resources.
+
+```js
+import { create } from '@platformatic/runtime'
+
+const app = await create('path/to/watt.json')
+await app.start()
+
+// Remove applications by ID
+const applicationsToRemove = ['service-1', 'service-2']
+
+await app.removeApplications(applicationsToRemove)
+```
+
+If `silent` is `true`, then logging will be suppressed during the removal process. Defaults to `false`.
+
+**Important**: The entrypoint application cannot be removed, attempting to do so will throw a `CannotRemoveEntrypointError`.
+
+### Example: Dynamic Service Management
+
+```js
+import { create, prepareApplication } from '@platformatic/runtime'
+
+const app = await create('path/to/watt.json')
+await app.start()
+
+// Add a new service dynamically
+const newService = await prepareApplication(app.getRuntimeConfig(true), {
+  id: 'analytics-service',
+  path: './analytics',
+  workers: 2
+})
+
+await app.addApplications([newService], true)
+
+// Later, remove it when no longer needed
+await app.removeApplications(['analytics-service'])
+```
+
 <Issues />

docs/reference/wattpm/cli-commands.md

@@ -23,6 +23,15 @@ npm install wattpm
 npx wattpm --help
 ```
 
+## Global Options
+
+These options are available for all `wattpm` commands:
+
+- `-r, --no-pretty` - Disable pretty-printed output for logs and console messages
+- `-v, --verbose` - Enable verbose output for detailed information
+- `-V, --version` - Display the current wattpm version
+- `-h, --help` - Show help information
+
 ## Core Watt Commands (`wattpm`)
 
 These are the primary commands for working with Watt applications: