From 89b4dfd7036e99d51aea427ae59d8ce7901b97b4 Mon Sep 17 00:00:00 2001 From: luke Date: Mon, 31 Jul 2006 22:48:44 +0000 Subject: adding ordering information git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1435 980ebf18-57e1-0310-9a29-db15c13687c0 --- documentation/documentation/big-picture.page | 1 + documentation/documentation/configref.page | 1 + .../documentation/creating-a-puppet-type.page | 1 + documentation/documentation/fromsvn.page | 1 + documentation/documentation/fsconfigref.page | 1 + documentation/documentation/howitworks.page | 1 + documentation/documentation/index.page | 3 +- documentation/documentation/installation.page | 1 + documentation/documentation/introduction.page | 1 + documentation/documentation/languagetutorial.page | 1 + documentation/documentation/ldapnodes.page | 1 + documentation/documentation/notcfengine.page | 1 + documentation/documentation/puppetshow.page | 71 ++++++++++++++++++++++ .../documentation/rails-puppet-manager.page | 70 --------------------- documentation/documentation/security.page | 1 + documentation/documentation/structures.page | 1 + documentation/documentation/testing.page | 1 + documentation/documentation/typedocs.page | 1 + 18 files changed, 88 insertions(+), 71 deletions(-) create mode 100644 documentation/documentation/puppetshow.page delete mode 100644 documentation/documentation/rails-puppet-manager.page diff --git a/documentation/documentation/big-picture.page b/documentation/documentation/big-picture.page index a828e25c2..a492c30ab 100644 --- a/documentation/documentation/big-picture.page +++ b/documentation/documentation/big-picture.page @@ -1,6 +1,7 @@ --- inMenu: true title: The Big Picture +orderInfo: 10 --- # Big picture diff --git a/documentation/documentation/configref.page b/documentation/documentation/configref.page index cb01f2806..6fba10b70 100644 --- a/documentation/documentation/configref.page +++ b/documentation/documentation/configref.page @@ -1,6 +1,7 @@ --- inMenu: true title: Configuration Reference +orderInfo: 6 --- # Puppet Configuration Reference diff --git a/documentation/documentation/creating-a-puppet-type.page b/documentation/documentation/creating-a-puppet-type.page index a9c23cafb..2ca27c842 100644 --- a/documentation/documentation/creating-a-puppet-type.page +++ b/documentation/documentation/creating-a-puppet-type.page @@ -1,6 +1,7 @@ --- inMenu: true title: Custom Types +orderInfo: 7 --- # Organizational Principles diff --git a/documentation/documentation/fromsvn.page b/documentation/documentation/fromsvn.page index 0e99579bb..218264d12 100644 --- a/documentation/documentation/fromsvn.page +++ b/documentation/documentation/fromsvn.page @@ -1,6 +1,7 @@ --- inMenu: true title: Using Source +orderInfo: 10 --- Puppet is currently implemented in Ruby and uses standard Ruby libraries. You should be able to run Puppet on any Unix-style host with Ruby. Windows diff --git a/documentation/documentation/fsconfigref.page b/documentation/documentation/fsconfigref.page index 911b709d5..a25d6d6be 100644 --- a/documentation/documentation/fsconfigref.page +++ b/documentation/documentation/fsconfigref.page @@ -1,6 +1,7 @@ --- inMenu: true title: Fileserver Configuration Reference +orderInfo: 8 --- # FileServer diff --git a/documentation/documentation/howitworks.page b/documentation/documentation/howitworks.page index ac14edddc..5d2780664 100644 --- a/documentation/documentation/howitworks.page +++ b/documentation/documentation/howitworks.page @@ -1,6 +1,7 @@ --- inMenu: true title: How It Works +orderInfo: 9 --- # Introduction diff --git a/documentation/documentation/index.page b/documentation/documentation/index.page index a566dea6a..10d829160 100644 --- a/documentation/documentation/index.page +++ b/documentation/documentation/index.page @@ -1,6 +1,7 @@ --- -inMenu: true +inMenu: false directoryName: Documentation +orderInfo: 1 subtreeLevel: 5 --- diff --git a/documentation/documentation/installation.page b/documentation/documentation/installation.page index 377bba64c..b4e484e90 100644 --- a/documentation/documentation/installation.page +++ b/documentation/documentation/installation.page @@ -1,5 +1,6 @@ --- inMenu: true +orderInfo: 3 --- # Comments diff --git a/documentation/documentation/introduction.page b/documentation/documentation/introduction.page index 837bbb305..e112d8dab 100644 --- a/documentation/documentation/introduction.page +++ b/documentation/documentation/introduction.page @@ -1,5 +1,6 @@ --- inMenu: true +orderInfo: 2 --- # Introduction diff --git a/documentation/documentation/languagetutorial.page b/documentation/documentation/languagetutorial.page index 413176b55..ccac0fc34 100644 --- a/documentation/documentation/languagetutorial.page +++ b/documentation/documentation/languagetutorial.page @@ -1,6 +1,7 @@ --- inMenu: true title: Language Tutorial +orderInfo: 5 --- # Elements and Organization diff --git a/documentation/documentation/ldapnodes.page b/documentation/documentation/ldapnodes.page index 265fcf877..388706191 100644 --- a/documentation/documentation/ldapnodes.page +++ b/documentation/documentation/ldapnodes.page @@ -1,6 +1,7 @@ --- inMenu: true title: LDAP Node Storage +orderInfo: 10 --- # Storing Node Information in LDAP diff --git a/documentation/documentation/notcfengine.page b/documentation/documentation/notcfengine.page index baa9bc0d0..7f36de2c3 100644 --- a/documentation/documentation/notcfengine.page +++ b/documentation/documentation/notcfengine.page @@ -1,6 +1,7 @@ --- inMenu: true title: Puppet vs. Cfengine +orderInfo: 10 --- [Cfengine](http://www.cfengine.org) is currently the most widely deployed diff --git a/documentation/documentation/puppetshow.page b/documentation/documentation/puppetshow.page new file mode 100644 index 000000000..41a882037 --- /dev/null +++ b/documentation/documentation/puppetshow.page @@ -0,0 +1,71 @@ +--- +inMenu: true +title: PuppetShow +orderInfo: 10 +--- + +I have begun work on a simplistic web-based Puppet manager based on +[Rails](http://rubyonrails.org), called PuppetShow. It's in a very primitive +state -- including having no authentication, so use at your own risk -- but +it's a good proof of concept. + +To get it working, first check out the +[code](https://reductivelabs.com/svn/puppetshow). Then set up your apache +config to serve it. This is what mine looks like: + + + ServerAdmin luke@madstop.com + SetEnv RAILS_ENV development + ServerName puppet.madstop.com + ServerAlias puppet + DocumentRoot /var/lib/puppetshow/public + ErrorLog /var/lib/puppetshow/log/apache.log + + + Options ExecCGI FollowSymLinks + AddHandler cgi-script .cgi + AllowOverride all + Order allow,deny + Allow from all + + + +Now we just need to get the puppet internal stuff working. We could use +either ``rake`` or Puppet to do this, but for whatever reason I decided to use +Puppet. I've created a ``setup.pp`` file in the root of the tree, so you just +need to modify that as appropriate (in particular, I have a Facter lib that +sets ``$home`` for me, so you'll probably need to set that), then run: + + sudo puppet -v setup.pp + +At that point you should have a functional app. Like I said, there's no +navigation at all, so you need to know what's out there. The first thing you +need to do is start a daemon that this app can connect to. Pick your victim, +create a namespace auth file (defaults to +``/etc/puppet/namespaceauth.conf``): + + [fileserver] + allow *.madstop.com + + [puppetmaster] + allow *.madstop.com + + [pelementserver] + allow puppet.madstop.com + +Then start your client: + + puppetd -v --listen --no-client + +Here we're telling it to start the listening daemon but not to run the config. +You can obviously use whatever options you want, though. + +Now you should be able to just go to your app. At this point, you need to +know the name of the machine you want to connect to and the name of a type to +look at. Say you're connecting to culain (my workstation's name), and you +want to look at users; this would be your URL: +http://puppet.domain.com/remote/culain/user/list + +Replace as appropriate for your site. + +*$Id$* diff --git a/documentation/documentation/rails-puppet-manager.page b/documentation/documentation/rails-puppet-manager.page deleted file mode 100644 index dda8295d5..000000000 --- a/documentation/documentation/rails-puppet-manager.page +++ /dev/null @@ -1,70 +0,0 @@ ---- -inMenu: true -title: PuppetShow ---- - -I have begun work on a simplistic web-based Puppet manager based on -[Rails](http://rubyonrails.org), called PuppetShow. It's in a very primitive -state -- including having no authentication, so use at your own risk -- but -it's a good proof of concept. - -To get it working, first check out the -[code](https://reductivelabs.com/svn/puppetshow). Then set up your apache -config to serve it. This is what mine looks like: - - - ServerAdmin luke@madstop.com - SetEnv RAILS_ENV development - ServerName puppet.madstop.com - ServerAlias puppet - DocumentRoot /var/lib/puppetshow/public - ErrorLog /var/lib/puppetshow/log/apache.log - - - Options ExecCGI FollowSymLinks - AddHandler cgi-script .cgi - AllowOverride all - Order allow,deny - Allow from all - - - -Now we just need to get the puppet internal stuff working. We could use -either ``rake`` or Puppet to do this, but for whatever reason I decided to use -Puppet. I've created a ``setup.pp`` file in the root of the tree, so you just -need to modify that as appropriate (in particular, I have a Facter lib that -sets ``$home`` for me, so you'll probably need to set that), then run: - - sudo puppet -v setup.pp - -At that point you should have a functional app. Like I said, there's no -navigation at all, so you need to know what's out there. The first thing you -need to do is start a daemon that this app can connect to. Pick your victim, -create a namespace auth file (defaults to -``/etc/puppet/namespaceauth.conf``): - - [fileserver] - allow *.madstop.com - - [puppetmaster] - allow *.madstop.com - - [pelementserver] - allow puppet.madstop.com - -Then start your client: - - puppetd -v --listen --no-client - -Here we're telling it to start the listening daemon but not to run the config. -You can obviously use whatever options you want, though. - -Now you should be able to just go to your app. At this point, you need to -know the name of the machine you want to connect to and the name of a type to -look at. Say you're connecting to culain (my workstation's name), and you -want to look at users; this would be your URL: -http://puppet.domain.com/remote/culain/user/list - -Replace as appropriate for your site. - -*$Id$* diff --git a/documentation/documentation/security.page b/documentation/documentation/security.page index 9e7c52e9c..086a2572d 100644 --- a/documentation/documentation/security.page +++ b/documentation/documentation/security.page @@ -1,5 +1,6 @@ --- inMenu: true +orderInfo: 10 --- # Overview diff --git a/documentation/documentation/structures.page b/documentation/documentation/structures.page index 93660abc1..40b665934 100644 --- a/documentation/documentation/structures.page +++ b/documentation/documentation/structures.page @@ -1,5 +1,6 @@ --- inMenu: true +orderInfo: 10 --- This is a brief overview of the language structures diff --git a/documentation/documentation/testing.page b/documentation/documentation/testing.page index f4b71f9d5..1f1ba9ba9 100644 --- a/documentation/documentation/testing.page +++ b/documentation/documentation/testing.page @@ -1,6 +1,7 @@ --- inMenu: true title: Testing +orderInfo: 10 --- If you want to just test-drive Puppet, making the least commitment possible, diff --git a/documentation/documentation/typedocs.page b/documentation/documentation/typedocs.page index bbfd86f25..368768239 100644 --- a/documentation/documentation/typedocs.page +++ b/documentation/documentation/typedocs.page @@ -1,6 +1,7 @@ --- inMenu: true title: Type Reference +orderInfo: 4 --- # Type Reference -- cgit