From 91d5670604e5a30fe27e12946ff6e876aafaa2e1 Mon Sep 17 00:00:00 2001 From: obarun <eric@obarun.org> Date: Sun, 17 Jan 2021 13:22:25 +1100 Subject: [PATCH] doc update --- doc/service-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/service-configuration-file.md b/doc/service-configuration-file.md index f7a26b03..0f370035 100644 --- a/doc/service-configuration-file.md +++ b/doc/service-configuration-file.md @@ -17,7 +17,7 @@ However, to suit your needs you may want to change a value of a `key=value` pair To accomplish this task, you have two solutions: -- use the [66-env](66-env.html) tool. This is the better and easy way to do it. This tool will take for you about the creation of the new file(if it doesn't exist yet) and allows you to edit it directly. +- use the [66-env](66-env.html) tool. This is the best and easy way to do it. This tool will take for you about the creation of the new file(if it doesn't exist yet) and allows you to edit it directly. - copy manually the `%%service_admconf%%/<service_name>/<service_version>/.service_name` to `%%service_admconf%%/<service_name>/<service_version>/service_name`. The copied file can be named as you want. At the service start process, the [execl-envfile](execl-envfile.html) tool will parses and reads every single file found at the `%%service_admconf%%/<service_name>/<service_version>/` directory in alphabetical order. That means that the upstream file will be read first than your modified file will be read. So, for a same `key=value` pair found at the upstream and modified file, the `key=value` pair coming from the modified file will be used. -- GitLab