helhum/env-ts

Writes environment variables as TypoScript constant file

This package is deprecated and will not be maintained any more

env ts

This is a composer plugin, that writes environment variables to a TypoScript constants file., _(*1)

This package is the missing link to be able to provide different TypoScript settings for TYPO3 installations in different environments., _(*2)

configuration options

You configure env ts in the extra section of a composer.json in any package like that:, _(*3)

  "extra": {
      "helhum/env-ts": {
          "files": {
              "path/to/environment.t3s": [
                  "PAGE__ROOT",
                  "PAGE__IMPRINT",
                  "PAGE__CUSTOMER_LOGIN"
              ]
          },
          "prefix": "environment",
          "array-delimiter": "__",
          "lower-camel-case": true
      }
    }

files [array]

Multiple files (path relative to package dir) can be specified as key and which environment variable prefixes should be included. In the above example it would have been enough to specify the prefix PAGE__, _(*4)

prefix [string]

By default environment variables are passed as is to the constants file. But it is possible to specify a prefix for the constants. In the above example environment.page.root is written for env var PAGE__ROOT, _(*5)

The default value is environment, _(*6)

array-delimiter [string]

By default environment variables are passed as is to the constants file. But it is possible to specify an array delimiter of the environment vars to be transformed into an array part of the constants. In the above example environment.page.root is written for env var PAGE__ROOT, _(*7)

The default value is __, _(*8)

lower-camel-case [bool]

Whether the constant name should rather be lower camel cased than totally upper cased. In the above example environment.page.customerLogin is written for env var PAGE__CUSTOMER_LOGIN, _(*9)

The default value is true., _(*10)

Feedback

Any feedback is appreciated. Please write bug reports, feature request, create pull requests, or just drop me a "thank you" via Twitter or spread the word., _(*11)

Thank you!, _(*12)