Changes between Version 7 and Version 8 of hct

Timestamp:

Jan 27, 2013, 9:47:24 PM (13 years ago)

Author:

Jamie McClelland

Comment:

--

hct

@@ -24 +24 @@
 == Getting Started ==
 
-hct can function on either a live or dev installation. As of December 2012 we only have a dev installation running.
+There is only one trouble program (and git repo in which it resides). However, there is both a live and dev repo of service advisory messages. If you create messages in the dev repo, you can practice releasing service advisories.
 
  * Checkout a copy of trouble via git:
@@ -32 +32 @@
 git config remote.origin.pushurl gitosis@git.mayfirst.org:mfpl/trouble
 }}}
- * Optionally symlink it in your ~/bin directory
- * Checkout a copy of the dev messages repo somewhere else:
+ * Optionally symlink it in your ~/bin directory (if you don't do this, you'll need to specify the full path to `trouble` everytime you run the program.
+ * Checkout a copy of either the live or the dev messages repo somewhere else:
 {{{
-git clone hct-dev@jojobe.mayfirst.org:/srv/hct-dev/messages/repo-hub hct-dev
+git clone hct-live@jojobe.mayfirst.org:/srv/hct-live/messages/repo-hub hct-live
 }}}
- * Try releasing a message:
+ * Releasing a message:
 {{{
-cd hct-dev
+cd hct-live
 /path/to/trouble message
 }}}
@@ -46 +46 @@
 Test rss: https://status.dev.mayfirst.org/rss.xml
 Test/Approve email: https://lists.mayfirst.org/mailman/admindb/service-advisories-dev
+
+Live html: https://status.dev.mayfirst.org/
+Live rss: https://status.dev.mayfirst.org/rss.xml
+Live/Approve email: https://lists.mayfirst.org/mailman/admindb/service-advisories-dev
 
 == trouble ==
@@ -56 +60 @@
 
 For usage, run trouble with no arguments:
-
 
 {{{