7
edits
Changes
→It's not needed after all
=== It's not needed after all ===
With Debian, there is no reason to actually use pre-built templates if you're not time-constrained in the deployment process and have other means of managing your configuration, since <tt>debootstrap</tt> is the tool at the core of every Debian installation and it doesn't matter if it's run by the [http://wiki.debian.org/DebianInstaller|Debian Installer], by hand or a completely different distribution.
Since <tt>debootstrap</tt> is the tool at the core of every Debian installation it doesn't matter if it's run by the [http://wiki.debian.org/DebianInstaller Debian Installer], during template creation, by hand or even in a completely different Linux distribution.
Management of configuration files by means of templates is a non-sustainable way of doing Configuration Management. In environments with few (if any) changes this can work out nicely, but in more agile/complex environments a proper Configuration Management solution should be used.
== Basic Steps ==
