gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-backoffice] branch master updated: Web application -


From: gnunet
Subject: [GNUnet-SVN] [taler-backoffice] branch master updated: Web application -> Web service.
Date: Thu, 18 Jan 2018 19:53:42 +0100

This is an automated email from the git hooks/post-receive script.

marcello pushed a commit to branch master
in repository backoffice.

The following commit(s) were added to refs/heads/master by this push:
     new e5715d4  Web application -> Web service.
e5715d4 is described below

commit e5715d4667e3e7ff282ec29c52dbe0a1847c32af
Author: Marcello Stanisci <address@hidden>
AuthorDate: Thu Jan 18 19:53:24 2018 +0100

    Web application -> Web service.
---
 doc/manual.texi | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/doc/manual.texi b/doc/manual.texi
index b0ff2e7..1db74fc 100644
--- a/doc/manual.texi
+++ b/doc/manual.texi
@@ -2,7 +2,7 @@
 @c %**start of header
 @setfilename manual.info
 @include version.texi
address@hidden Back-office Web application manual @value{VERSION}.
address@hidden Back-office Web service manual @value{VERSION}.
 
 @c Define a new index for options.
 @defcodeindex op
@@ -31,7 +31,7 @@ Texts.  A copy of the license is included in the section 
entitled
 @c Titlepage
 @c
 @titlepage
address@hidden Back-office Web application manual.
address@hidden Back-office Web service manual.
 @subtitle Version @value{VERSION}
 @subtitle @value{UPDATED}
 @author Marcello Stanisci (@email{marcello@@taler.net})
@@ -46,21 +46,21 @@ Texts.  A copy of the license is included in the section 
entitled
 
 @ifnottex
 @node Top
address@hidden Back-office Web application manual.
address@hidden Back-office Web service manual.
 @insertcopying
 @end ifnottex
 
 @menu
-* Introduction::                           What services the Web application 
provides.
+* Introduction::                           What is provided by the Web service.
 * Installation::                           Where to find the code and how to 
install it.
-* Configuration::                          How to configure the Web 
application.
-* Launching the backoffice::               How to run the Web application.
+* Configuration::                          How to configure the Web service.
+* Launching the backoffice::               How to run the Web service.
 @end menu
 
 @node Introduction
 @chapter Introduction
 
-The back-office Web application allows a merchant to check on the status
+The back-office Web service allows a merchant to check on the status
 of their Taler transactions.  Merchants can check if and when they were
 paid by a wire transfer for coins deposited at the exchange.  Also, given
 a wire transfer they have received, they can ask which Taler transactions
@@ -72,7 +72,7 @@ installation and configuration of this Web service.
 @node Installation
 @chapter Installation
 
-The back-office Web application code is available at
+The back-office Web service code is available at
 @code{git://taler.net/backoffice}.  The application can be installed
 in a GNU-ish fashion.
 
@@ -99,11 +99,11 @@ included in the @code{$PATH}, and
 
 The following information must be provided in the configuration: on which
 address the backend should serve the Web site, which currency is used,
-and which merchant backend this Web application will work with.
+and which merchant backend this Web service will work with.
 
 The merchant backend is an important agent, as it is responsible for
 returning information about transactions and wire transfers.  The
-backoffice Web application is merely a frontend for it.  A separate
+backoffice Web service is merely a frontend for it.  A separate
 manual (available at
 @url{https://docs.taler.net/merchant/backend/html/manual.html})
 describes the installation and configuration of the merchant backend.
@@ -119,7 +119,7 @@ a working configuration example is the following one:
 # works with.
 currency = KUDOS
 
-# each back-office Web application is associated with a "frontend
+# each back-office Web service is associated with a "frontend
 # name": this name instructs the application which configuration
 # section is going to be read.  Thus <name> is the "frontend name"
 # and must be specified on the command line via the "--frontend"
@@ -158,7 +158,7 @@ instances = <instance_1> <instance_2> ..
 @node Launching the backoffice
 @chapter Launching the backoffice
 
-The following example shows how to run the Web application.
+The following example shows how to run the Web service.
 
 @example
 # such invocation will work only if the configuration contains

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]