Update gh-pages to output generated at ab55a2a

nightly/_sources/concepts/orders.md.txt

@@ -170,7 +170,7 @@ order: MarketOrder = self.order_factory.market(
     quantity=Quantity.from_int(100_000),
     time_in_force=TimeInForce.IOC,  # <-- optional (default GTC)
     reduce_only=False,  # <-- optional (default False)
-    tags="ENTRY",  # <-- optional (default None)
+    tags=["ENTRY"],  # <-- optional (default None)
 )
 ```
 [API Reference](https://docs.nautilustrader.io/api_reference/model/orders.html#module-nautilus_trader.model.orders.market)
@@ -324,7 +324,7 @@ order: MarketIfTouchedOrder = self.order_factory.market_if_touched(
     time_in_force=TimeInForce.GTC,  # <-- optional (default GTC)
     expire_time=None,  # <-- optional (default None)
     reduce_only=False,  # <-- optional (default False)
-    tags="ENTRY",  # <-- optional (default None)
+    tags=["ENTRY"],  # <-- optional (default None)
 )
 ```
 
@@ -359,7 +359,7 @@ order: StopLimitOrder = self.order_factory.limit_if_touched(
     expire_time=pd.Timestamp("2022-06-06T12:00"),
     post_only=True,  # <-- optional (default False)
     reduce_only=False,  # <-- optional (default False)
-    tags="TAKE_PROFIT",  # <-- optional (default None)
+    tags=["TAKE_PROFIT"],  # <-- optional (default None)
 )
 ```
 
@@ -396,7 +396,7 @@ order: TrailingStopMarketOrder = self.order_factory.trailing_stop_market(
     time_in_force=TimeInForce.GTC,  # <-- optional (default GTC)
     expire_time=None,  # <-- optional (default None)
     reduce_only=True,  # <-- optional (default False)
-    tags="TRAILING_STOP-1",  # <-- optional (default None)
+    tags=["TRAILING_STOP-1"],  # <-- optional (default None)
 )
 ```
 
@@ -436,7 +436,7 @@ order: TrailingStopLimitOrder = self.order_factory.trailing_stop_limit(
     time_in_force=TimeInForce.GTC,  # <-- optional (default GTC)
     expire_time=None,  # <-- optional (default None)
     reduce_only=True,  # <-- optional (default False)
-    tags="TRAILING_STOP",  # <-- optional (default None)
+    tags=["TRAILING_STOP"],  # <-- optional (default None)
 )
 ```
 

nightly/_sources/developer_guide/environment_setup.md.txt

@@ -32,3 +32,93 @@ Following any changes to `.pyx` or `.pxd` files, you can re-compile by running:
 or
 
     make build
+
+## Services
+You can use `docker-compose.yml` file located in `.docker` directory 
+to bootstrap the Nautilus working environment. This will start the following services:
+
+```bash
+docker-compose up -d
+```
+
+If you only want specific services running (like `postgres` for example), you can start them with command:
+
+```bash
+docker-compose up -d postgres
+```
+
+Used services are:
+
+- `postgres` - Postgres database with root user `POSTRES_USER` which defaults to `postgres`, `POSTGRES_PASSWORD` which defaults to `pass` and `POSTGRES_DB` which defaults to `postgres`
+- `redis` - Redis server
+- `pgadmin` - PgAdmin4 for database management and administration
+
+> **Note:** Please use this as development environment only. For production, use a proper and  more secure setup.
+
+After the services has been started, you must log in with `psql` cli to create `nautilus` Postgres database.
+To do that you can run, and type `POSTGRES_PASSWORD` from docker service setup
+
+```bash
+psql -h localhost -p 5432 -U postgres
+```
+
+After you have logged in as `postgres` administrator, run `CREATE DATABASE` command with target db name (we use `nautilus`): 
+
+```
+psql (16.2, server 15.2 (Debian 15.2-1.pgdg110+1))
+Type "help" for help.
+
+postgres=# CREATE DATABASE nautilus;
+CREATE DATABASE
+
+```
+
+## Nautilus CLI Developer Guide
+
+## Introduction
+
+The Nautilus CLI is a command-line interface tool designed to interact
+with the Nautilus Trader ecosystem. It provides commands for managing the Postgres database and other trading operations.
+
+> **Note:** The Nautilus CLI command is only supported on UNIX-like systems.
+
+
+## Install 
+
+You can install nautilus cli command with from Make file target, which will use `cargo install` under the hood.
+And this command will install `nautilus` bin executable in your path if Rust `cargo` is properly configured.
+
+```bash
+make install-cli
+```
+
+## Commands
+You can run `nautilus --help` to inspect structure of CLI and groups of commands:
+
+### Database
+These are commands related to the bootstrapping the Postgres database.
+For that you work, you need to supply right connection configuration. You can do that through 
+command line arguments or `.env` file in the root directory or where the commands is being run.
+
+- `--host` arg or `POSTGRES_HOST` for database host
+- `--port` arg or `POSTGRES_PORT` for database port
+- `--user` arg or `POSTGRES_USER` for root administrator user to run command with (namely `postgres` root user here)
+- `--password` arg or `POSTGRES_PASSWORD` for root administrator password
+- `--database` arg or `POSTGRES_DATABASE` for both database **name and new user** that will have privileges of this database
+  ( if you provided `nautilus` as value, then new user will be created with name `nautilus` that will inherit the password from `POSTGRES_PASSWORD`
+ and `nautilus` database with be bootstrapped with this user as owner)
+
+Example of `.env` file
+
+```
+POSTGRES_HOST=localhost
+POSTGRES_PORT=5432
+POSTGRES_USERNAME=postgres
+POSTGRES_DATABASE=nautilus
+POSTGRES_PASSWORD=pass
+```
+
+List of commands are:
+
+1. `nautilus database init` - it will bootstrap schema, roles and all sql files located in `schema` root directory (like `tables.sql`)
+2. `nautilus database drop` - it will drop all tables, role and data in target Postgres database

nightly/api_reference/adapters/interactive_brokers.html

@@ -12085,7 +12085,7 @@ <h2 id="module-nautilus_trader.adapters.interactive_brokers.config">
               at
              </span>
              <span class="pre">
-              0x7f54ba1aeb90&gt;
+              0x7fcfbc772b50&gt;
              </span>
              <span class="pre">
               =