RuneCMS is intended to be a simple, lightweight tool for building and deploying static websites.

It’s based on Livetext, but could be generalized to be agnostic of that tool. It is abstracted from a portion of RuneBlog.

In its present form, the ‘rcms command simply takes a parameter. Your choices are: .xtable

‘[ rcms config]

Initialize ‘config.txt if necessary and edit with `vi

‘[ rcms generate]

Find stale files under ‘source/ and generate them under `target/

‘[ rcms view]

View the current state of ‘target/ via browser (local files)

‘[ rcms publish]

Publish ‘target/ to the remote server

‘[ rcms browse]

Browse the current state of the remote server

.end

At present, there is no check for these to be done in order. For example, you could publish without a generate (analogous to editing a C program and running the executable without recompiling it).

The assumption is made that keys for the user and server are already set up. The ‘config.txt file looks like:

<pre> server: foo.com path: /var/www/foo user: hal9000 </pre>

More details later…