Parameterize everything! Variables provide an easy way to avoid hard-coding all sorts of things in your system, environment or project.
-
Put environment specific settings in one or more environment configuration files. This allows you to deploy your project to another environment (dev/uat/prod) without changing your project, you’ll only need to configure another set of configuration files.
-
When referencing file locations, prefer
${PROJECT_HOME}
over expressions like${Internal.Entry.Current.Directory}
or${Internal.Pipeline.Filename.Directory}
-
Configure transform copies with variables to allow for easy transition between differently sized environments.
-
use the Environment Variables to keep your projects and environments, audit information etc outside of your Apache Hop installation.