Add documentation for Truffle Dashboard

src/docs/truffle/getting-started/using-the-truffle-dashboard.md

@@ -0,0 +1,104 @@
+---
+title: Using the Truffle Dashboard
+layout: docs.hbs
+---
+# Using the Truffle Dashboard
+
+When deploying your smart contracts you need to specify an Ethereum account that has enough funds to cover the transaction fees of the deployment. A popular method of doing this is copy-pasting your mnemonic phrase to a gitignored `.env` file so that it can be used for e.g. the `@truffle/hdwallet-provider`. But in general it is a bad practice to copy-paste your keys, especially since we have wallets like MetaMask that can send transactions for us.
+
+This is why we developed the Truffle Dashboard, an easy way to use your existing MetaMask wallet for your deployments and for other transactions that you need to send from a command line context. Because the Truffle Dashboard connects directly to MetaMask it is also possible to use it in combination with hardware wallets like Ledger or Trezor.
+
+## Starting a dashboard
+
+To start a Truffle Dashboard, you need to run the `truffle dashboard` command in a separate terminal window.
+
+```
+> truffle dashboard [--port <number>] [--host <string>] [--verbose]
+
+Truffle Dashboard running at http://localhost:24012
+DashboardProvider RPC endpoint running at http://localhost:24012/rpc
+```
+
+By default, this starts a dashboard at `http://localhost:24012` and opens the dashboard in a new tab in your default browser. The Dashboard then prompts you to connect your wallet and confirm that you're connected to the right network. You should double check your connected network at this point, since switching to a different network during a deployment can have unintended consequences.
+
+![Connect your wallet to the Truffle Dashboard](/img/docs/truffle/using-the-truffle-dashboard/truffle-dashboard-connect.png)
+
+![Confirm your connected network](/img/docs/truffle/using-the-truffle-dashboard/truffle-dashboard-confirm.png)
+
+The port and host can be configured through command line options, or by configuring them inside your `truffle-config.js`.
+
+```js
+module.exports = {
+  // ... rest of truffle config
+
+  dashboard: {
+    port: 24012,
+  }
+
+  networks: {
+    // ... network configurations, including the network named 'dashboard'
+  }
+}
+```
+
+
+## Connecting to the dashboard
+
+To make connecting to the Truffle Dashboard easy, Truffle includes a builtin network named "dashboard". This builtin network automatically uses the port and host specified in the dashboard config or falls back to the default `http://localhost:24012`. This builtin network can be used with all your deployments or scripts.
+
+```
+truffle migrate --network dashboard
+truffle console --network dashboard
+```
+
+From there every Ethereum RPC request will be forwarded from Truffle to the Truffle Dashboard, where the user can inspect the RPC requests and process them with MetaMask.
+
+![Truffle Dashboard Transaction](/img/docs/truffle/using-the-truffle-dashboard/truffle-dashboard-transaction.png)
+
+Any additional network options or overrides can be provided by adding a network called "dashboard" to your `truffle-config.js` file and providing network options like it were a regular network.
+
+```js
+module.exports = {
+  // ... rest of truffle config
+
+  networks: {
+    // ... rest of network config
+
+    dashboard: {
+      networkCheckTimeout: 120000,
+    }
+  }
+
+  dashboard: {
+    // ... dashboard host/port config
+  }
+};
+```
+
+
+## Usage with non-Truffle tooling
+
+We know that not everyone uses Truffle for their smart contract development, but we believe that the Truffle Dashboard should be accessible to everyone. This is why we developed the Truffle Dashboard to be agnostic of the tools you're using, so it can also be used with other tools such as Hardhat.
+
+When using the Truffle Dashboard with Hardhat, you need to create a network configuration inside your `hardhat.config.js` file that specifies the Truffle Dashboard's RPC URL.
+
+```js
+module.exports = {
+  // ... rest of hardhat config
+
+  networks: {
+    // ... rest of network config
+
+    'truffle-dashboard': {
+      url: "http://localhost:24012/rpc"
+    }
+  },
+};
+```
+
+From there it can be used with any Hardhat tasks as well as tools like hardhat-deploy.
+
+```
+hardhat deploy --network truffle-dashboard
+```
+

src/docs/truffle/reference/configuration.md

@@ -272,6 +272,19 @@ module.exports = {
 };
 ```
 
+### dashboard
+
+Configuration options for the [Truffle Dashboard](/docs/truffle/getting-started/using-the-truffle-dashboard.html). These options will be used when running `truffle dashboard` inside the project directory and these details will be used for the builtin "dashboard" network.
+
+Example:
+
+```javascript
+module.exports = {
+  port: 24012,
+  host: "localhost",
+  verbose: false,
+};
+```
 
 ### mocha
 

src/docs/truffle/reference/truffle-commands.md

@@ -98,6 +98,36 @@ Options:
 
 Camel case names of artifacts will be converted to underscore-separated file names for the migrations and tests. Number prefixes for migrations are automatically generated.
 
+### dashboard
+
+Start and open an instance of the Truffle dashboard.
+
+```shell
+truffle dashboard [--port <number>] [--host <string>] [--verbose]
+```
+
+Options:
+
+* `--port <number>`: Port to start the Truffle dashboard on (default `24012`).
+* `--host <string>`: Host to start the Truffle dashboard on (default `localhost`).
+* `--verbose`: Start the Truffle dashboard with additional verbose logging (default `false`)
+
+It is also possible to specify these options in the `truffle-config.js` file under `"dashboard"`. For example:
+
+```js
+module.exports = {
+  // ... rest of truffle config
+
+  dashboard: {
+    port: 25012,
+    host: "localhost",
+    verbose: true
+  }
+}
+```
+
+When specifying options in the config file *and* in the CLI, the options provided in the CLI take precedence.
+
 ### debug
 
 Interactively debug any transaction on the blockchain.