This is an automated email from the ASF dual-hosted git repository. hansva pushed a commit to branch hansva-patch-1 in repository https://gitbox.apache.org/repos/asf/hop.git
commit 15cbad4d3799f5fdd41a89fb6ee8450b7d97c9e0 Author: Hans Van Akelyen <[email protected]> AuthorDate: Fri Feb 3 09:50:53 2023 +0100 remove variable notation from HOP_CONFIG_FOLDER --- docs/hop-user-manual/modules/ROOT/pages/projects/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hop-user-manual/modules/ROOT/pages/projects/index.adoc b/docs/hop-user-manual/modules/ROOT/pages/projects/index.adoc index 83327a9249..fcbfc44752 100644 --- a/docs/hop-user-manual/modules/ROOT/pages/projects/index.adoc +++ b/docs/hop-user-manual/modules/ROOT/pages/projects/index.adoc @@ -45,7 +45,7 @@ To match standard development best practices you would check all these files int TIP: project variables should only be used when you need variables on the project level. All variables to connect to infrastructure, e.g. database connection parameters, mail servers etc that take different values in different environments should be created at the environment level. -TIP: Project configurations are stored in hop-config.json, which is read from `hop/config` by default. Use the `{openvar}HOP_CONFIG_FOLDER{closevar}` operating system variable to store your Hop configuration in a folder outside your Hop folder. This will let you keep your project list if you switch Hop installations or upgrade to a newer Hop version. +TIP: Project configurations are stored in hop-config.json, which is read from `hop/config` by default. Use the `HOP_CONFIG_FOLDER` operating system variable to store your Hop configuration in a folder outside your Hop folder. This will let you keep your project list if you switch Hop installations or upgrade to a newer Hop version. Projects can inherit metadata and variables from a parent project.
