runecms 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0b1cf72aae9cef64f3ee6b67563d364b64dc642ac9f78e4e16c5c7de052de2d1
-  data.tar.gz: 119e1a1fc184a131037ea83fc17b2ebbc4bf3808391932209b6da1f48ca64054
+  metadata.gz: b4f884b2be197b244c34f98bc85a84685e3fa40182fce1f6678f163ec6808f73
+  data.tar.gz: b633b9cd4b0431690035de81aef184924012e03c3348e1c58cd1d76bbc52e933
 SHA512:
-  metadata.gz: adbcaa106ba6f15871a0a5f7ba46acbac83c4fd2dea6687cb1090faa3c45e6a41c770cb65ed4ebf50555615830d6b40cdbbee0076a087f875da3bb091d08ed77
-  data.tar.gz: 6e65de46de4debb221845983380ecb98408b3ddb5db1a8bbe57c9845b7c4f2ab91e5bbeebf52a4266bbe203a507cdb72c2f680368edfb2bf89710f72604eb261
+  metadata.gz: 8cf5e5919123322d67b0fe0b9737fb6757a0aed9eda477fde7f1d871963db4485b97767ced676f171f3960c145180daf33bea80497b165d966ac13315a2e945b
+  data.tar.gz: 2e0c6632ab668f77a74b1432309e3cce56a462256fdf16c2efd2c23dbb09de35d051d9d27ad3dc9feb5b37be3fbf6f5f15ffd582d44cd6c1d22bd6012b14f794

data/README.lt3

@@ -1,21 +1,35 @@
+. Note: at present, paragraphs are broken in livetext. Hence the .br
+
 RuneCMS is intended to be a simple, lightweight tool for building
 and deploying static websites.
 
+.br 2
+
 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.
-These are:
+.br 2
+
+In its present form, the `rcms command simply takes a parameter.
+Choices are:
+
+.br 2
 
 .xtable
+`[rcms version] :: Print the version number of RuneCMS
+
 `[rcms config] :: Initialize `config.txt if necessary and edit with `vi
 
-`[rcms generate] :: Find stale files under `source/ and generate them under `target/
+`[rcms check] ::  List stale files, but do nothing else
 
-`[rcms view] :: View the current state of `target/ via browser (local files)
+`[rcms generate] :: Find stale files under `source/ and generate them under `target/
 
 `[rcms publish] :: Publish `target/ to the remote server
 
+`[rcms update]  :: Shortcut - Like a generate followed by a publish
+
+`[rcms view] :: View the current state of `target/ via browser (local files)
+
 `[rcms browse] :: Browse the current state of the remote server
 .end
 
@@ -23,6 +37,8 @@ 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).
 
+.br 2
+
 The assumption is made that keys for the user and server are already 
 set up. The `config.txt file looks like:
 
@@ -34,23 +50,33 @@ user: hal9000
 
 <hr>
 
+*[Original notes:]
+
 <pre>
-Idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
+General idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
 and rsync to upload.
 
+.br 2
+
 Config will comprise:
   - server
   - user
   - root/path
 
+.br 2
+
 Dir structure:
 
+.br 2
+
   site
    |
    +---- config.lt3
    +---- source/...
    +---- target/...
 
+.br 2
+
 Logic flow:
   1. Edit file(s) under source/ tree
   2. Generate 
@@ -64,5 +90,7 @@ Logic flow:
 
 </pre>
 
+.br 2
+
 More details later...
 

data/README.md

@@ -1,10 +1,19 @@
 RuneCMS is intended to be a simple, lightweight tool for building
 and deploying static websites.
+<br><br>
 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 <t>rcms`</t> command simply takes a parameter.
-These are:
+<br><br>
+In its present form, the <t>rcms</t> command simply takes a parameter.
+Choices are:
+<br><br>
 <br><center><table width=90% cellpadding=5>
+<tr>
+  <td valign=top><t>rcms version</t></td>
+  <td valign=top>Print the version number of RuneCMS</td>
+</tr>
+<tr>
+</tr>
 <tr>
   <td valign=top><t>rcms config</t></td>
   <td valign=top>Initialize <t>config.txt</t> if necessary and edit with <t>vi</t></td>
@@ -12,14 +21,14 @@ These are:
 <tr>
 </tr>
 <tr>
-  <td valign=top><t>rcms generate</t></td>
-  <td valign=top>Find stale files under <t>source/</t> and generate them under <t>target/</t></td>
+  <td valign=top><t>rcms check</t></td>
+  <td valign=top> List stale files, but do nothing else</td>
 </tr>
 <tr>
 </tr>
 <tr>
-  <td valign=top><t>rcms view</t></td>
-  <td valign=top>View the current state of <t>target/</t> via browser (local files)</td>
+  <td valign=top><t>rcms generate</t></td>
+  <td valign=top>Find stale files under <t>source/</t> and generate them under <t>target/</t></td>
 </tr>
 <tr>
 </tr>
@@ -29,6 +38,18 @@ These are:
 </tr>
 <tr>
 </tr>
+<tr>
+  <td valign=top><t>rcms update</t> </td>
+  <td valign=top>Shortcut - Like a generate followed by a publish</td>
+</tr>
+<tr>
+</tr>
+<tr>
+  <td valign=top><t>rcms view</t></td>
+  <td valign=top>View the current state of <t>target/</t> via browser (local files)</td>
+</tr>
+<tr>
+</tr>
 <tr>
   <td valign=top><t>rcms browse</t></td>
   <td valign=top>Browse the current state of the remote server</td>
@@ -37,6 +58,7 @@ These are:
 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).
+<br><br>
 The assumption is made that keys for the user and server are already 
 set up. The <t>config.txt</t> file looks like:
 <pre>
@@ -45,19 +67,24 @@ path: /var/www/foo
 user: hal9000
 </pre>
 <hr>
+<b>Original notes:</b>
 <pre>
-Idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
+General idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
 and rsync to upload.
+<br><br>
 Config will comprise:
   - server
   - user
   - root/path
+<br><br>
 Dir structure:
+<br><br>
   site
    |
    +---- config.lt3
    +---- source/...
    +---- target/...
+<br><br>
 Logic flow:
   1. Edit file(s) under source/ tree
   2. Generate 
@@ -69,4 +96,5 @@ Logic flow:
   4. Publish via rsync
       # cmd = "rsync -r -z #{target}/ #@user@#@server:#{path}/"
 </pre>
+<br><br>
 More details later...

data/lib/runecms/support.rb

@@ -9,6 +9,14 @@ def usage_message
     rcms publish   Publish target/ to the remote server
     rcms update    Shortcut - Like a generate followed by a push
     rcms browse    Browse the current state of the remote server
+
+    Run from a directory with a config.txt, a source/ dir, and a target/ dir.
+
+    Config file looks like:
+      server: example.com
+      path: /some/arbitrary/path
+      user: myuser
+
   TEXT
   puts
   exit

data/lib/runecms/version.rb

@@ -1,3 +1,3 @@
 class RuneCMS
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

data/runecms.gemspec

@@ -7,9 +7,7 @@ Gem::Specification.new do |s|
   def s.file_trees(*dirs)
     list = []
     dirs.each do |dir| 
-      puts "dir = #{dir}"
       stuff = Find.find(dir).to_a 
-      puts "  #{stuff.inspect}"
       list += stuff
     end
     list
@@ -37,4 +35,5 @@ Gem::Specification.new do |s|
   s.files       =  main + misc
   s.homepage    = 'https://github.com/Hal9000/runecms'
   s.license     = "Ruby"
+  s.post_install_message = "\n  Success! For help, run 'rcms' with no parameters.\n "
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: runecms
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Hal Fulton
@@ -33,7 +33,7 @@ homepage: https://github.com/Hal9000/runecms
 licenses:
 - Ruby
 metadata: {}
-post_install_message:
+post_install_message: "\n  Success! For help, run 'rcms' with no parameters.\n "
 rdoc_options: []
 require_paths:
 - lib