To facilitate simpler customization and easier adoption of the tool, I suggest creating a generic customization layer or config extension that can accommodate the most common customization cases. The cases I recognize are:
- Running commands on target
- Running commands on host
- Pushing files to the target
With a built-in customization layer, it could look something like this:
customizer:
chroot:
- useradd -m -s /bin/bash -u 4000 $IGconf_device_user1
command:
- date > $1/etc/imagetime
file1source: ../myconf
file1target: /etc/myconf
If the config file format would accommodate the same directly instead, it could essentially pass through mmdebstrap same as layers:
mmdebstrap:
customize-hooks:
- chroot $1 sh -c "useradd -m -s /bin/bash -u 4000 $IGconf_device_user1"
- date > $1/etc/imagetime
- cp ../myconf $1/etc/myconf
To facilitate simpler customization and easier adoption of the tool, I suggest creating a generic customization layer or config extension that can accommodate the most common customization cases. The cases I recognize are:
With a built-in customization layer, it could look something like this:
If the config file format would accommodate the same directly instead, it could essentially pass through mmdebstrap same as layers: