From 645c515033988c4d52a2c2dfdf28ef916bdd8b07 Mon Sep 17 00:00:00 2001 From: Matteo Mortari Date: Sat, 11 Feb 2023 11:03:42 +0100 Subject: [PATCH] TIP quarkus-systemd-notify when deploy to systemd implemented review feedback --- docs/src/main/asciidoc/container-image.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/src/main/asciidoc/container-image.adoc b/docs/src/main/asciidoc/container-image.adoc index 754caaf679fa4..3ba0df3b44a37 100644 --- a/docs/src/main/asciidoc/container-image.adoc +++ b/docs/src/main/asciidoc/container-image.adoc @@ -209,6 +209,13 @@ For example, if both `container-image-docker` and `container-image-s2i` are pres quarkus.container-image.builder=docker ---- +== Integrating with `systemd-notify` + +If you are building a container image in order to deploy your Quarkus application as a Linux service with Podman and Systemd, you might want to consider including the https://quarkiverse.github.io/quarkiverse-docs/quarkus-systemd-notify/dev/index.html[Quarkus Systemd Notify Extension] as part of your application, with: + +:add-extension-extensions: io.quarkiverse.systemd.notify:quarkus-systemd-notify +include::{includes}/devtools/extension-add.adoc[] + == Customizing The following properties can be used to customize the container image build process.