From 4e4a74b4911c3e08aeac5eeb9848ff1c0f887142 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Stroi=C5=84ski?= Date: Wed, 26 Nov 2025 15:07:00 +0000 Subject: [PATCH 1/5] Fix a typo in #duct/include example --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index a4bb8c8..1d0453e 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -725,7 +725,7 @@ own configuration file, and also have a separate configuration for the {:vars #duct/include "vars.edn" :system {:duct.module/logging {} - :tutorial.print/hello #duct.include "hello.edn"}} + :tutorial.print/hello #duct/include "hello.edn"}} ---- .vars.edn From 2856db585fdf28e672cd92f6532adc3d2c8474a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Stroi=C5=84ski?= Date: Wed, 26 Nov 2025 21:03:16 +0000 Subject: [PATCH 2/5] Add missing 'are' --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index 1d0453e..5c5c56d 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -1037,7 +1037,7 @@ We add a new key, `:todo.middleware/wrap-headers`, which configures and creates the middleware function, then we use an Integrant ref to add that function to a vector of middleware. -There three ways to apply middleware: +There are three ways to apply middleware: * Middleware is applied to all requests (via `:middleware`) * Middleware is applied if any route matches (via `:route-middleware`) From 4027de8fa2318f6dd0db10c7014f3a5687bd267b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Stroi=C5=84ski?= Date: Wed, 10 Dec 2025 11:28:09 +0000 Subject: [PATCH 3/5] int the system -> in the system --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index 5c5c56d..a12a81c 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -1753,7 +1753,7 @@ and check the web application at: === Deployment -During development we typically run every key int the system, but when +During development we typically run every key in the system, but when we deploy, it's often useful to run a subset. We can specify which keys to run with the `--keys` option. This will From 08fc23e539e81a31672fee2a2e09670be4f83770 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Stroi=C5=84ski?= Date: Wed, 10 Dec 2025 11:44:43 +0000 Subject: [PATCH 4/5] the it -> it --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index a12a81c..71039ab 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -1837,7 +1837,7 @@ that looks like this: ---- In order to run this configuration, you have a main function that loads -in the config file and populates the it with additional values from the +in the config file and populates it with additional values from the environment. In the example below, the server port number is pulled from the `PORT` environment variable. From 454c6cd17e7ba569678ac1acc276c348f296c386 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Stroi=C5=84ski?= Date: Wed, 10 Dec 2025 14:50:41 +0000 Subject: [PATCH 5/5] in order [to] avoid --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index 71039ab..a33f29c 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -1993,7 +1993,7 @@ the host machine's port 3000 so you can access your application at: This container is configured to only run keys deriving from `:duct/daemon` (and those it references). This includes keys like `:duct.server.http/jetty` provided by the web module. This will exclude -migrations in order avoid multiple containers behind a load balancer all +migrations in order to avoid multiple containers behind a load balancer all trying to update the database at once. In order to run the migrations, you'll need to run Duct in your