Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • dev
  • resolve
  • parser
  • patch-1
  • async
  • boot
  • state
  • 0.8.0.2
  • 0.8.0.1
  • 0.8.0.0
  • 0.7.2.1
  • 0.7.2.0
  • 0.7.1.1
  • 0.7.1.0
  • 0.7.0.2
  • 0.7.0.1
  • 0.7.0.0
  • 0.7.0.0-preprod-rev2
  • 0.7.0.0-preprod-rev1
  • 0.7.0.0-preprod
  • 0.7.0.0-beta-3
  • 0.7.0.0-beta-2
  • 0.7.0.0-beta
  • v0.6.2.0
  • v0.6.1.3
  • v0.6.1.2
  • v0.6.1.1
28 results
Blame Permalink
service-configuration-file.md 1.89 KiB

title: The 66 Suite: service configuration file author: Eric Vidal eric@obarun.org

66

Software

obarun.org

Service configuration file

If the env options at the @options field is set to a frontend service file, the [environment] section is copied to the %%service_admconf%%/<service_name>/<service_version>/.service_name file.

Note: The file name is prefixed with a dot.

This file is always written at 66-enable call. That means that every single changes made on this file will be lost. This is ensure you to you always have the environment variables set by upstream matching the needs of the service to be started properly.

However, to suit your needs you may want to change a value of a key=value pair or and a new one for a modified service. In that case, you need to make a copy of the upstream file to a new file at %%service_admconf%%/<service_name>/<service_version>/ directories.

To accomplish this task, you have two solutions:

  • use the 66-env 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 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.