From b9c73fca5f590173c5e2fa17d244e851e982ba0d Mon Sep 17 00:00:00 2001 From: Holly Cummins Date: Wed, 14 Aug 2024 17:26:41 +0100 Subject: [PATCH] Review comments from Guillaume --- docs/src/main/asciidoc/extension-writing-dev-service.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/extension-writing-dev-service.adoc b/docs/src/main/asciidoc/extension-writing-dev-service.adoc index 1afb950e9b344..18fb564c63f77 100644 --- a/docs/src/main/asciidoc/extension-writing-dev-service.adoc +++ b/docs/src/main/asciidoc/extension-writing-dev-service.adoc @@ -18,7 +18,7 @@ include::_attributes.adoc[] - You should already have an xref:building-my-first-extension.adoc[extension structure] in place - You should have a containerised version of your external service (not all dev services rely on containers, but most do) -== Creating a dev service +== Creating a Dev Service If your extension provides APIs for connecting to an external service, it's a good idea to provide a xref:dev-services.adoc[dev service] implementation. @@ -104,7 +104,7 @@ You may wish to use this config to set a fixed port, or set an image name, for e == Controlling re-use -In dev mode, with hot reload, Quarkus may restart frequently. By default, this will also restart test containers. +In dev mode, with live reload, Quarkus may restart frequently. By default, this will also restart test containers. Quarkus restarts are usually very fast, but containers may take much longer to restart. To prevent containers restarting on every code change, you can mark the container as reusable: