puppet and bolt - online edit of handbook/troggle/troglaptop.html

This commit is contained in:
2025-07-17 09:20:40 +01:00
committed by Expo on server
parent 0b266539ac
commit af04e379ab

View File

@@ -115,9 +115,11 @@ which you can read without installing by looking in:<br>
<p>But there is the significant danger that containers would get copied around and deployed without being properly cleaned up:
resulting in configuration drift and a <a href="https://martinfowler.com/bliki/SnowflakeServer.html">snowflake server situation</a>.
File permissions are a big issue.
<h4>Configuration management</h4>
<p>We should eventually have both a Container, for getting started quickly, and a separate recipe-based
build system so that systems are rebuilt cleanly from the basics, to avoid the <a href="https://martinfowler.com/bliki/SnowflakeServer.html">snowflake issue</a>. <a href="http://www.cuyc.org.uk">CUYC</a> (who also use Django) have a bash script which sets up a new django
development system and we have something similar, but it is fragile. A recipe-based build system instead of a string of commands would be better, e.g. <a href="https://en.wikipedia.org/wiki/List_of_build_automation_software">Qbs</a>.
build system so that systems are rebuilt cleanly from the basics, to avoid the <a href="https://martinfowler.com/bliki/SnowflakeServer.html">snowflake issue</a>.
<p><a href="http://www.cuyc.org.uk">CUYC</a> (who also use Django) have a bash script which sets up a new django
development system and we have something similar, but it is fragile. A target-based build system instead of a string of commands would be a better idea, e.g. <a href="https://www.puppet.com/blog/puppet-vs-chef">puppet</a> or <a href="https://help.puppet.com/bolt/current/topics/getting_started_with_bolt.htm">bolt</a>.
<h2 id="git">Configuring ubuntu</h2>