Piro / YUKI Hiroshi
null+****@clear*****
Tue Sep 23 19:25:50 JST 2014
Piro / YUKI Hiroshi 2014-09-23 19:25:50 +0900 (Tue, 23 Sep 2014) New Revision: 99f5e6ac0e81ac1a35eccbd170267152607b126f https://github.com/droonga/droonga.org/commit/99f5e6ac0e81ac1a35eccbd170267152607b126f Message: Always markup pre formatted text by "~~~" instead of indentations Modified files: tutorial/1.0.6/dump-restore/index.md tutorial/1.0.6/groonga/index.md Modified: tutorial/1.0.6/dump-restore/index.md (+19 -11) =================================================================== --- tutorial/1.0.6/dump-restore/index.md 2014-09-23 19:24:53 +0900 (5c50256) +++ tutorial/1.0.6/dump-restore/index.md 2014-09-23 19:25:50 +0900 (a0bb8a4) @@ -24,12 +24,16 @@ If you have Droonga nodes with other names, read `node0` and `node1` in followin First, install a command line tool named `drndump` via rubygems: - # gem install drndump +~~~ +# gem install drndump +~~~ After that, establish that the `drndump` command has been installed successfully: - $ drndump --version - drndump 1.0.0 +~~~ +$ drndump --version +drndump 1.0.0 +~~~ ### Dump all data in a Droonga cluster @@ -97,9 +101,11 @@ Note to these things: The result is printed to the standard output. To save it as a JSONs file, you'll use a redirection like: - $ drndump --host=node0 \ - --receiver-host=node2 \ - > dump.jsons +~~~ +$ drndump --host=node0 \ + --receiver-host=node2 \ + > dump.jsons +~~~ ## Restore data to a Droonga cluster @@ -111,12 +117,16 @@ The result of `drndump` command is a list of Droonga messages. You need to use `droonga-send` command to send it to your Droogna cluster. Install the command included in the package `droonga-client`, via rubygems: - # gem install droonga-client +~~~ +# gem install droonga-client +~~~ After that, establish that the `droonga-send` command has been installed successfully: - $ droonga-send --version - droonga-send 0.1.9 +~~~ +$ droonga-send --version +droonga-send 0.1.9 +~~~ ### Prepare an empty Droonga cluster @@ -438,8 +448,6 @@ $ curl "http://node1:10041/d/select?table=Store&output_columns=name&limit=10" | ] ~~~ -Note: `/droonga/system/status` may not return the result like above. It can cache the result of old status. We have to update these codes to confirm cluster changes. - ### Duplicate data between two Droonga clusters Modified: tutorial/1.0.6/groonga/index.md (+11 -5) =================================================================== --- tutorial/1.0.6/groonga/index.md 2014-09-23 19:24:53 +0900 (da1216b) +++ tutorial/1.0.6/groonga/index.md 2014-09-23 19:25:50 +0900 (2a434a1) @@ -205,15 +205,19 @@ Let's continue to [the next step, "how to use the cluster"](#use). You can run Groonga as an HTTP server daemon with the option `-d`, like: - # groonga -p 10041 -d --protocol http /tmp/databases/db +~~~ +# groonga -p 10041 -d --protocol http /tmp/databases/db +~~~ On the other hand, you have to run multiple server daemons for each Droonga node to use your Droonga cluster via HTTP. If you set up your Droonga nodes by installation scripts, daemons are already been configured as system services managed via the `service` command. To start them, run commands like following on each Droonga node: - # service droonga-engine start - # service droonga-http-server start +~~~ +# service droonga-engine start +# service droonga-http-server start +~~~ If you set up your Droonga nodes manually, see [the manual installation tutorial](../manual-install/#start-services). @@ -258,8 +262,10 @@ $ curl "http://node1:10041/droonga/system/status" | jq "." To stop services, run commands like following on each Droonga node: - # service droonga-engine stop - # service droonga-http-server stop +~~~ +# service droonga-engine stop +# service droonga-http-server stop +~~~ If you set up your Droonga nodes manually, see [the manual installation tutorial](../manual-install/#stop-services). -------------- next part -------------- HTML����������������������������... Download