From 9c3edacde671481abaa76dba88ca53ca58a70338 Mon Sep 17 00:00:00 2001 From: Thomas Gauvin <35609369+thomasgauvin@users.noreply.github.com> Date: Tue, 2 Sep 2025 13:17:20 -0400 Subject: [PATCH 1/4] Add development mode instructions to get-started.mdx Added instructions for running in development mode. --- src/content/docs/hyperdrive/get-started.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/hyperdrive/get-started.mdx b/src/content/docs/hyperdrive/get-started.mdx index b1590edae7bc505..1e174c6971bedab 100644 --- a/src/content/docs/hyperdrive/get-started.mdx +++ b/src/content/docs/hyperdrive/get-started.mdx @@ -341,6 +341,10 @@ Upon receiving a request, the code above does the following: +## 5. Run in development mode (optional) + +You can start your project in development mode. If you want to connect to a local database on your local development computer (ie: `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. + ## 6. Deploy your Worker You can now deploy your Worker to make your project accessible on the Internet. To deploy your Worker, run: From 16211365f4c19b5cd4fca443622507d883173a52 Mon Sep 17 00:00:00 2001 From: Jun Lee Date: Wed, 3 Sep 2025 09:12:54 +0100 Subject: [PATCH 2/4] Update src/content/docs/hyperdrive/get-started.mdx --- src/content/docs/hyperdrive/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/hyperdrive/get-started.mdx b/src/content/docs/hyperdrive/get-started.mdx index 1e174c6971bedab..b6eff81cd5c715c 100644 --- a/src/content/docs/hyperdrive/get-started.mdx +++ b/src/content/docs/hyperdrive/get-started.mdx @@ -343,7 +343,7 @@ Upon receiving a request, the code above does the following: ## 5. Run in development mode (optional) -You can start your project in development mode. If you want to connect to a local database on your local development computer (ie: `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. +You can start your project in development mode. If you want to connect to a local database on your local development computer (i.e. `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect, and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. ## 6. Deploy your Worker From 096137fd18afebf7ab422e8ded63002d665a4df2 Mon Sep 17 00:00:00 2001 From: Thomas Gauvin <35609369+thomasgauvin@users.noreply.github.com> Date: Wed, 3 Sep 2025 09:54:47 -0400 Subject: [PATCH 3/4] Update src/content/docs/hyperdrive/get-started.mdx --- src/content/docs/hyperdrive/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/hyperdrive/get-started.mdx b/src/content/docs/hyperdrive/get-started.mdx index b6eff81cd5c715c..2033d9a9588be03 100644 --- a/src/content/docs/hyperdrive/get-started.mdx +++ b/src/content/docs/hyperdrive/get-started.mdx @@ -341,7 +341,7 @@ Upon receiving a request, the code above does the following: -## 5. Run in development mode (optional) +### Run in development mode (optional) You can start your project in development mode. If you want to connect to a local database on your local development computer (i.e. `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect, and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. From d3f256f56bd39ada26970845b18233d30300007f Mon Sep 17 00:00:00 2001 From: Thomas Gauvin <35609369+thomasgauvin@users.noreply.github.com> Date: Fri, 5 Sep 2025 10:36:04 -0400 Subject: [PATCH 4/4] Update src/content/docs/hyperdrive/get-started.mdx --- src/content/docs/hyperdrive/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/hyperdrive/get-started.mdx b/src/content/docs/hyperdrive/get-started.mdx index 2033d9a9588be03..8c5965314423d90 100644 --- a/src/content/docs/hyperdrive/get-started.mdx +++ b/src/content/docs/hyperdrive/get-started.mdx @@ -343,7 +343,7 @@ Upon receiving a request, the code above does the following: ### Run in development mode (optional) -You can start your project in development mode. If you want to connect to a local database on your local development computer (i.e. `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect, and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. +You can start your project in development mode. If you want to connect to the local database configured in your `wrangler.jsonc` with `localConnectionString` (e.g. `localhost:5432`), you can now run `wrangler dev`. This will connect directly to your database from your local Worker project emulation (Hyperdrive caching will not take effect, and the local database must not require SSL). To develop using a remote database, you can connect to your Hyperdrive configuration by running `wrangler dev --remote`. ## 6. Deploy your Worker