Making your work portable is one of the best advice to keep things simple when it's time to deploy the work into a different environment. If you move your work to another machine or another folder, or the path to source or destination files changes, or the connection properties to the databases change, the idea is that everything keeps working without or with minimal changes. There are a couple of things that you can do when you pursue this objective:
- Don't use fixed names but variables. As mentioned before, this applies to database connections, project folders, remote servers, among others. If you know the values of the variables beforehand, define the variables in the kettle.properties file.
- For the location of ...
