Server automation framework and application
Перейти к файлу
Luke Kanies c45c5c4fff renaming
git-svn-id: https://reductivelabs.com/svn/puppet/library/trunk@110 980ebf18-57e1-0310-9a29-db15c13687c0
2005-04-13 18:20:25 +00:00
bin reorganizing 2005-04-13 15:23:57 +00:00
examples reorganizing 2005-04-13 15:23:57 +00:00
lib renaming 2005-04-13 18:20:25 +00:00
notes reorganizing 2005-04-13 15:23:57 +00:00
test adding package source, initially including only files as a source 2005-04-13 16:27:43 +00:00
CHANGELOG reorganizing 2005-04-13 15:25:00 +00:00
Install reorganizing 2005-04-13 15:25:00 +00:00
README reorganizing 2005-04-13 15:23:57 +00:00
install.rb reorganizing 2005-04-13 15:23:57 +00:00

README

$Id$

Introduction
============
There are currently three main components to Blink:

Objects
-------
These are the "primitives" of the language.  If you want to affect the system,
these are the only way to do it.  Their base class is in blink/objects.rb, and
they all inherit directly from that class.

Attributes
----------
Each of the Objects are basically a collection of attributes.  The attributes
themselves are how the system is actually modified -- e.g., you set
'file("/etc/passwd").owner = X', which modifies an attribute value, and that
results in the system itelf being modified.

Each attribute derives from blink/attribute.rb, but most attributes are actually
defined in the same file as the class that uses them (e.g., blink/objects/file.rb).

The Wrapper
-----------
At the top level is the Blink module.  It doesn't do much right now

Starting
========
You can start with bin/blinker, but it's probably better to just start in test/.
I've been writing simple unit tests for most of the work I've done, so you can
see how things do (and should) work by looking in there.  Just run 'ruby
<testfile>'.