From fd864286ab88ae674de45fbbb0717f2b7c2182c4 Mon Sep 17 00:00:00 2001 From: luke Date: Sun, 3 Sep 2006 01:31:11 +0000 Subject: Updating templating docs with more about usage, and adding installation notes about ruby segfaults on Debian git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1532 980ebf18-57e1-0310-9a29-db15c13687c0 --- documentation/documentation/installation.page | 9 +++++++-- documentation/documentation/templating.page | 24 ++++++++++++++++-------- 2 files changed, 23 insertions(+), 10 deletions(-) diff --git a/documentation/documentation/installation.page b/documentation/documentation/installation.page index d33ebcdd6..f4e9860ec 100644 --- a/documentation/documentation/installation.page +++ b/documentation/documentation/installation.page @@ -98,13 +98,18 @@ this is the package dependency list for Puppet on Debian: Note that **libruby1.8** versions above **1.8.4-1** on Debian/testing seem to be broken, resulting in segfaults. Until an update gets released to fix -this, you should pin library1.8, by putting something like the following into -``/etc/apt/preferences``: +this, you should pin to library1.8, by putting something like the following +into ``/etc/apt/preferences``: Package: libruby1.8 Pin: version 1.8.4-1 Pin-Priority: 1001 +If you have already upgraded your library1.8 package, you can downgrade it by +adding ``deb http://snapshot.debian.net/archive pool ruby1.8`` to your +``/etc/apt/sources.list`` and then running +``apt-get install libruby1=1.8.4-1``. + #### SuSE Martin Vuk is maintaining a SuSE diff --git a/documentation/documentation/templating.page b/documentation/documentation/templating.page index 654fea468..73865429d 100644 --- a/documentation/documentation/templating.page +++ b/documentation/documentation/templating.page @@ -14,6 +14,12 @@ templates in Puppet's ``templatedir``, which usually defaults to ``/var/puppet/templates`` (you can find out what it is on your system by running ``puppet --configprint templatedir``). +Templates are always evaluated by the parser, not by the client. This means +that if you are using ``puppetmasterd``, then the templates only need to be on +the server, and you never need to download them to the client. There's +no difference to the client between using a template and specifying +all of the text as a string. + Templating is pretty simple: You can reference any variables within your template that are defined within the enclosing scope. This is especially useful for generating complete files; here is how I generate the Apache @@ -41,17 +47,17 @@ configuration for my [Trac](http://trac.edgewall.org/) sites: And then here's my template: 

-
You can see that I put each Trac configuration into a separate file, and then @@ -73,9 +79,7 @@ is an array, you can iterate over it. Given Puppet code like this: You could have a template like this: 

-    <% values.each do |val| %>
-    Some stuff with <%= val %>
-    <% end%>
+    <% values.each do |val| %> Some stuff with <%= val %> <% end%>
This would produce: @@ -84,6 +88,10 @@ This would produce: Some stuff with val2 Some stuff with otherval +Note that ERB template lines that just have code on them get translated into +blank lines, so if you were to split the above code into three lines, you +would get two blank lines between each line of output. + Internally, Puppet's values get translated to real Ruby values, including ``true`` and ``false``, so you can be pretty confident that variables will behave as you might expect. -- cgit