Forum archive
TKLPatch init point for TKLBAM
Hi, all; I am absolutely new to TKL and blown away by this project's elegance!
I would like to know if it is possible to build a custom appliance utilizing TKLPatch and have that be your init point for TKLBAM backups. For example, if you start with the TKL LAMP appliance and use TKLPatch to bring in git, samba, etc, is it then possible to set up TKLBAM to use this new appliance as the initial reference point for updates rather than the 'original' LAMP appliance?
To be explicit: As I undertand it, with a fresh install of the TKL LAMP appliance, your initial backup with TKLBAM is negligible in size. If you then proceed to update the appliance with several application installs, your next incremental backup can be quite extensive. Is it possible to set up your custom appliance and use this as the initial reference point for TKLBAM or are the initialization parameters 'hard-wired' to the existing official appliances?
The good news is that from the start TKLBAM was conceived with the aim of supporting more completely community development, in supplement to TKLPatch, so the user scenario you suggest (or something like it) may be supported more fully in the future. In the present, the inefficiency shouldn't be a show stopper, just a lack of optimization.