docs: updated with new features and fixes

Author: Akalanka47000

docs/auditing/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Auditing",
-  "position": 11,
+  "position": 12,
   "link": {
     "type": "generated-index"
   }

docs/auditing/enable-auditing.md

@@ -16,6 +16,8 @@ It internally makes use of the `Triggers` defined within Elemental. This means t
 CastleModel.EnableAuditing()
 ```
 
+#### Alternatively you can pass `Audting` as `true` within the schema options when creating a new model.
+
 ## TODO
 
 - [ ] Implement concurrency control to make sure that the same audit log is not written multiple times.

docs/benchmarks/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Benchmarks",
-  "position": 13,
+  "position": 15,
   "link": {
     "type": "generated-index"
   }

docs/cli/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "CLI",
+  "position": 11,
+  "link": {
+    "type": "generated-index"
+  }
+}

docs/cli/commands/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "Commands",
+  "position": 2,
+  "link": {
+    "type": "generated-index"
+  }
+}

docs/cli/commands/init.md

@@ -0,0 +1,53 @@
+---
+sidebar_position: 1
+---
+
+# Init
+
+Initializes a new default configuration file for the Elemental CLI.
+
+```bash
+elemental init
+```
+
+You can also specify a MongoDB connection string as an argument to the command. This will be used as the connection string in the configuration file.
+
+```bash
+elemental init mongodb://localhost:27017
+```
+
+## The configuration file
+
+The elemental config file is a YAML or JSON file with one of the following names:
+
+- .elementalrc
+- .elemental.yaml
+- .elemental.yml
+- elemental.json
+- elemental.yaml
+- elemental.yml
+
+The default configuration file is `.elementalrc`. The configuration file is created in the current working directory when you run the `elemental init` command. If a configuration file already exists, it will not be overwritten.
+
+## Example configuration file
+
+```json
+{
+  "connection_str": "mongodb://localhost:27017",
+  "migrations_dir": "database/migrations",
+  "seeds_dir": "database/seeds",
+  "changelog_collection": "changelog"
+}
+```
+
+### Environment variables
+
+The elemental config file also supports reading from environment variables. For example, you can specify the `connection_str` as `<DB_CONNECTION_STRING>` in the config file, and it will be replaced with the value of the `DB_CONNECTION_STRING` environment variable during runtime.
+
+```json
+{
+  "connection_str": "<DB_CONNECTION_STRING>"
+}
+```
+
+If a `.env` file is present in the same directory as the config file, it will pick up the environment variables from there. It also uses the environemnt variable `APP_ENV` to look for .env file variants if specified. If the `APP_ENV` variable is set to `production`, it will look for a `.env.production` file. If it is set to `development`, it will look for a `.env.development` file. The environment variables are loaded using the [**godotenv**](https://github.com/joho/godotenv) package.

docs/cli/commands/migrate.md

@@ -0,0 +1,31 @@
+---
+sidebar_position: 2
+---
+
+# Migrate
+
+Create, apply and rollback migrations using the Elemental CLI.
+
+## Create a migration
+
+The migration file will be created in the `migrations_dir` specified in the configuration file. By default, this is `database/migrations`.
+
+```bash
+elemental migrate create <migration_name>
+```
+
+## Run migrations
+
+Run all pending migrations. This will create a changelog collection in the database if it does not exist. By default, this is `changelog`.
+
+```bash
+elemental migrate up
+```
+
+## Rollback migrations
+
+Rollback the last migration. This will remove the last entry in the changelog collection.
+
+```bash
+elemental migrate down
+```

docs/cli/commands/seed.md

@@ -0,0 +1,31 @@
+---
+sidebar_position: 3
+---
+
+# Seed
+
+Create, apply and rollback seeds using the Elemental CLI.
+
+## Create a seeder
+
+The seeder will be created in the `seeds_dir` specified in the configuration file. By default, this is `database/seeds`.
+
+```bash
+elemental seed create <seeder_name>
+```
+
+## Run seeders
+
+Run all pending seeds. This will create a changelog collection in the database if it does not exist. By default, this is `changelog`.
+
+```bash
+elemental seed up
+```
+
+## Rollback seeders
+
+Rollback the last seed. This will remove the last entry in the changelog collection.
+
+```bash
+elemental seed down
+```

docs/cli/index.md

@@ -0,0 +1,11 @@
+---
+sidebar_position: 1
+---
+
+# Installation
+
+The Elemental CLI is a command-line tool that helps you manage stuff such as migrations and seeders. It is still in its early stages, but it is already quite useful. You can install it with the following command:
+
+```bash
+go install github.com/elcengine/elemental@latest
+```

docs/cross-connection-queries/switching-collections.md

@@ -7,7 +7,7 @@ sidebar_position: 4
 The Elemental ORM allows you to switch between different collections in the middle of a query. This is useful when you have multiple collections and you need to query data from both.
 
 ```go
-witchers := WitcherModel.Find().SetCollection("secondary-collection").Exec().([]Witcher)
+witchers := WitcherModel.Find().SetCollection("secondary-collection").ExecTT()
 ```
 
 In the example above, we are switching the collection to `secondary-collection` before executing the query. This will ensure that the query is executed on the `secondary-collection` collection.