Doc Config

Configuration (i.e. the "receipe" to cook the image) is done by defining bash key/value pairs in "./bootstrap.cfg" (must be in same directory as the "bootstrap.sh" script)

a minimal working example bootstrap.cfg file would look like this:

RPI_PLUGINS=("raspbian")

It would just download the default latest raspbian-lite and extract the image.

builtin config variables

name	description	default value
RPI_BOOTSTRAP_PLUGINS	run those plugins in this order	()
RPI_HOSTNAME	hostname the image will use	unnamed
RPI_PLUGINDIR	path to plugins	./bootstrap-plugins
RPI_DISTDIR	s. dist dir	./bootstrap_dist
RPI_WORKDIR	work dir. can be removed at any time to start from scratch	./.bootstrap-work
RPI_TMPDIR	temporary dir	/tmp
RPI_USER_PLUGINDIR	user specific plugins. If a plugin exists here, it will be prefered over the one in RPI_PLUGINDIR	~/.bootstrap-plugins
RPI_USER_DISTDIR	user specific distdir. If files exist here, they will be prefered over the ones in RPI_DISTDIR	~/.bootstrap-dist
RPI_USER_CONFIG	user specific config. Additional to the project's bootstrap.cfg	~/.bootstrap.cfg
RPI_ROOT	mountpoint for root partition	./.bootstrap-work/root
RPI_BOOT	mountpoint for boot partition	./.bootstrap-work/boot

~/.bootstrap.cfg

To customize default behaviour, .bootstrap.cfg will be included from the $HOME directory. It will override settings from after the project specific bootstrap.cfg.

Also, ~/.bootstrap-plugins can contain user specific plugins and ~/.bootstrap-dist user distfiles.

Plugins

s. Plugin overview for plugin specific config options.