Operations

Operations make it possible to execute custom code before and after the data seeding happens. The configuration is done inside the main configuration file.

Operations are configured below the operations property. Each operation requires a unique identifier that contains the operation configuration.

For creating custom operations, see the Operations page.

This extension provides the following operations by default:

DotEnv Generator

This operation generates an env-file with configurable contents. Mostly used to get UIDs mapped to an env variable that can be used in TYPO3 (e.g. for 404 page).

operations:
    envFileGenerator:
      envFiles:
        pids:
          path: pids.env
          values:
            PID_404: "{pages:404:uid}"

Name	Type	Required
envFiles	object	true
envFiles.<identifier>.path	string	true
envFiles.<identifier>.values	object	true

envFiles

Type: object
Required: true

Can contain multiple key/identifiers. Each key represents one env-file.

envFiles.<identifier>.path

Type: string
Required: true

Relative path and filename for the env-file that should be generated.

envFiles.<identifier>.values

Type: object
Required: true

An object containing key/value pairs that are put into the env-file. Values can use variables and combined identifiers as well as static values.

values:
  IS_SEEDED_DATA: "1"
  PID_404: "{pages:404:uid}"