runecms 0.0.3 → 0.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0b1cf72aae9cef64f3ee6b67563d364b64dc642ac9f78e4e16c5c7de052de2d1
4
- data.tar.gz: 119e1a1fc184a131037ea83fc17b2ebbc4bf3808391932209b6da1f48ca64054
3
+ metadata.gz: b4f884b2be197b244c34f98bc85a84685e3fa40182fce1f6678f163ec6808f73
4
+ data.tar.gz: b633b9cd4b0431690035de81aef184924012e03c3348e1c58cd1d76bbc52e933
5
5
  SHA512:
6
- metadata.gz: adbcaa106ba6f15871a0a5f7ba46acbac83c4fd2dea6687cb1090faa3c45e6a41c770cb65ed4ebf50555615830d6b40cdbbee0076a087f875da3bb091d08ed77
7
- data.tar.gz: 6e65de46de4debb221845983380ecb98408b3ddb5db1a8bbe57c9845b7c4f2ab91e5bbeebf52a4266bbe203a507cdb72c2f680368edfb2bf89710f72604eb261
6
+ metadata.gz: 8cf5e5919123322d67b0fe0b9737fb6757a0aed9eda477fde7f1d871963db4485b97767ced676f171f3960c145180daf33bea80497b165d966ac13315a2e945b
7
+ data.tar.gz: 2e0c6632ab668f77a74b1432309e3cce56a462256fdf16c2efd2c23dbb09de35d051d9d27ad3dc9feb5b37be3fbf6f5f15ffd582d44cd6c1d22bd6012b14f794
data/README.lt3 CHANGED
@@ -1,21 +1,35 @@
1
+ . Note: at present, paragraphs are broken in livetext. Hence the .br
2
+
1
3
  RuneCMS is intended to be a simple, lightweight tool for building
2
4
  and deploying static websites.
3
5
 
6
+ .br 2
7
+
4
8
  It's based on Livetext, but could be generalized to be agnostic of
5
9
  that tool. It is abstracted from a portion of RuneBlog.
6
10
 
7
- In its present form, the `rcms` command simply takes a parameter.
8
- These are:
11
+ .br 2
12
+
13
+ In its present form, the `rcms command simply takes a parameter.
14
+ Choices are:
15
+
16
+ .br 2
9
17
 
10
18
  .xtable
19
+ `[rcms version] :: Print the version number of RuneCMS
20
+
11
21
  `[rcms config] :: Initialize `config.txt if necessary and edit with `vi
12
22
 
13
- `[rcms generate] :: Find stale files under `source/ and generate them under `target/
23
+ `[rcms check] :: List stale files, but do nothing else
14
24
 
15
- `[rcms view] :: View the current state of `target/ via browser (local files)
25
+ `[rcms generate] :: Find stale files under `source/ and generate them under `target/
16
26
 
17
27
  `[rcms publish] :: Publish `target/ to the remote server
18
28
 
29
+ `[rcms update] :: Shortcut - Like a generate followed by a publish
30
+
31
+ `[rcms view] :: View the current state of `target/ via browser (local files)
32
+
19
33
  `[rcms browse] :: Browse the current state of the remote server
20
34
  .end
21
35
 
@@ -23,6 +37,8 @@ At present, there is no check for these to be done in order. For example,
23
37
  you could publish without a generate (analogous to editing a C program
24
38
  and running the executable without recompiling it).
25
39
 
40
+ .br 2
41
+
26
42
  The assumption is made that keys for the user and server are already
27
43
  set up. The `config.txt file looks like:
28
44
 
@@ -34,23 +50,33 @@ user: hal9000
34
50
 
35
51
  <hr>
36
52
 
53
+ *[Original notes:]
54
+
37
55
  <pre>
38
- Idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
56
+ General idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
39
57
  and rsync to upload.
40
58
 
59
+ .br 2
60
+
41
61
  Config will comprise:
42
62
  - server
43
63
  - user
44
64
  - root/path
45
65
 
66
+ .br 2
67
+
46
68
  Dir structure:
47
69
 
70
+ .br 2
71
+
48
72
  site
49
73
  |
50
74
  +---- config.lt3
51
75
  +---- source/...
52
76
  +---- target/...
53
77
 
78
+ .br 2
79
+
54
80
  Logic flow:
55
81
  1. Edit file(s) under source/ tree
56
82
  2. Generate
@@ -64,5 +90,7 @@ Logic flow:
64
90
 
65
91
  </pre>
66
92
 
93
+ .br 2
94
+
67
95
  More details later...
68
96
 
data/README.md CHANGED
@@ -1,10 +1,19 @@
1
1
  RuneCMS is intended to be a simple, lightweight tool for building
2
2
  and deploying static websites.
3
+ <br><br>
3
4
  It's based on Livetext, but could be generalized to be agnostic of
4
5
  that tool. It is abstracted from a portion of RuneBlog.
5
- In its present form, the <t>rcms`</t> command simply takes a parameter.
6
- These are:
6
+ <br><br>
7
+ In its present form, the <t>rcms</t> command simply takes a parameter.
8
+ Choices are:
9
+ <br><br>
7
10
  <br><center><table width=90% cellpadding=5>
11
+ <tr>
12
+ <td valign=top><t>rcms version</t></td>
13
+ <td valign=top>Print the version number of RuneCMS</td>
14
+ </tr>
15
+ <tr>
16
+ </tr>
8
17
  <tr>
9
18
  <td valign=top><t>rcms config</t></td>
10
19
  <td valign=top>Initialize <t>config.txt</t> if necessary and edit with <t>vi</t></td>
@@ -12,14 +21,14 @@ These are:
12
21
  <tr>
13
22
  </tr>
14
23
  <tr>
15
- <td valign=top><t>rcms generate</t></td>
16
- <td valign=top>Find stale files under <t>source/</t> and generate them under <t>target/</t></td>
24
+ <td valign=top><t>rcms check</t></td>
25
+ <td valign=top> List stale files, but do nothing else</td>
17
26
  </tr>
18
27
  <tr>
19
28
  </tr>
20
29
  <tr>
21
- <td valign=top><t>rcms view</t></td>
22
- <td valign=top>View the current state of <t>target/</t> via browser (local files)</td>
30
+ <td valign=top><t>rcms generate</t></td>
31
+ <td valign=top>Find stale files under <t>source/</t> and generate them under <t>target/</t></td>
23
32
  </tr>
24
33
  <tr>
25
34
  </tr>
@@ -29,6 +38,18 @@ These are:
29
38
  </tr>
30
39
  <tr>
31
40
  </tr>
41
+ <tr>
42
+ <td valign=top><t>rcms update</t> </td>
43
+ <td valign=top>Shortcut - Like a generate followed by a publish</td>
44
+ </tr>
45
+ <tr>
46
+ </tr>
47
+ <tr>
48
+ <td valign=top><t>rcms view</t></td>
49
+ <td valign=top>View the current state of <t>target/</t> via browser (local files)</td>
50
+ </tr>
51
+ <tr>
52
+ </tr>
32
53
  <tr>
33
54
  <td valign=top><t>rcms browse</t></td>
34
55
  <td valign=top>Browse the current state of the remote server</td>
@@ -37,6 +58,7 @@ These are:
37
58
  At present, there is no check for these to be done in order. For example,
38
59
  you could publish without a generate (analogous to editing a C program
39
60
  and running the executable without recompiling it).
61
+ <br><br>
40
62
  The assumption is made that keys for the user and server are already
41
63
  set up. The <t>config.txt</t> file looks like:
42
64
  <pre>
@@ -45,19 +67,24 @@ path: /var/www/foo
45
67
  user: hal9000
46
68
  </pre>
47
69
  <hr>
70
+ <b>Original notes:</b>
48
71
  <pre>
49
- Idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
72
+ General idea: Website is stored in a directory tree. Use Livetext (etc.?) to create target files
50
73
  and rsync to upload.
74
+ <br><br>
51
75
  Config will comprise:
52
76
  - server
53
77
  - user
54
78
  - root/path
79
+ <br><br>
55
80
  Dir structure:
81
+ <br><br>
56
82
  site
57
83
  |
58
84
  +---- config.lt3
59
85
  +---- source/...
60
86
  +---- target/...
87
+ <br><br>
61
88
  Logic flow:
62
89
  1. Edit file(s) under source/ tree
63
90
  2. Generate
@@ -69,4 +96,5 @@ Logic flow:
69
96
  4. Publish via rsync
70
97
  # cmd = "rsync -r -z #{target}/ #@user@#@server:#{path}/"
71
98
  </pre>
99
+ <br><br>
72
100
  More details later...
@@ -9,6 +9,14 @@ def usage_message
9
9
  rcms publish Publish target/ to the remote server
10
10
  rcms update Shortcut - Like a generate followed by a push
11
11
  rcms browse Browse the current state of the remote server
12
+
13
+ Run from a directory with a config.txt, a source/ dir, and a target/ dir.
14
+
15
+ Config file looks like:
16
+ server: example.com
17
+ path: /some/arbitrary/path
18
+ user: myuser
19
+
12
20
  TEXT
13
21
  puts
14
22
  exit
@@ -1,3 +1,3 @@
1
1
  class RuneCMS
2
- VERSION = "0.0.3"
2
+ VERSION = "0.0.4"
3
3
  end
data/runecms.gemspec CHANGED
@@ -7,9 +7,7 @@ Gem::Specification.new do |s|
7
7
  def s.file_trees(*dirs)
8
8
  list = []
9
9
  dirs.each do |dir|
10
- puts "dir = #{dir}"
11
10
  stuff = Find.find(dir).to_a
12
- puts " #{stuff.inspect}"
13
11
  list += stuff
14
12
  end
15
13
  list
@@ -37,4 +35,5 @@ Gem::Specification.new do |s|
37
35
  s.files = main + misc
38
36
  s.homepage = 'https://github.com/Hal9000/runecms'
39
37
  s.license = "Ruby"
38
+ s.post_install_message = "\n Success! For help, run 'rcms' with no parameters.\n "
40
39
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: runecms
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.3
4
+ version: 0.0.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Hal Fulton
@@ -33,7 +33,7 @@ homepage: https://github.com/Hal9000/runecms
33
33
  licenses:
34
34
  - Ruby
35
35
  metadata: {}
36
- post_install_message:
36
+ post_install_message: "\n Success! For help, run 'rcms' with no parameters.\n "
37
37
  rdoc_options: []
38
38
  require_paths:
39
39
  - lib