taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 296063ebe0aef4ee94eed7068fc5500e52708703
parent 1a97c102696ff76d25fd1cc83eaee2110f114df5
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue, 23 Jun 2020 10:30:51 +0200

Merge branch 'master' of git+ssh://git.taler.net/docs

Diffstat:
Mdevelopers-manual.rst | 16++++++++--------
Mtaler-wallet.rst | 5+++++
2 files changed, 13 insertions(+), 8 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst @@ -28,7 +28,7 @@ Developer's Manual .. note:: - This manual contains information for developers working on GNU Taler + This manual contains information for developers working on GNU Taler and related components. It is not intended for a general audience. .. contents:: Table of Contents @@ -324,7 +324,7 @@ Here are some highlights: - The WORKER is the config that that lives on a shell account on a localhost (taler.net), where this host has buildbot-worker installed. The WORKER executes the commands that perform all end-functions of buildbot. -- The WORKER running buildbot-worker receives these commands by authenticating and communicating with the buildbot server using parameters that were specified when the worker was created in that shell account with the `buildbot-worker` command. +- The WORKER running buildbot-worker receives these commands by authenticating and communicating with the buildbot server using parameters that were specified when the worker was created in that shell account with the ``buildbot-worker`` command. - The buildbot server's master.cfg file contains FACTORY declarations which specify the commands that the WORKER will run on localhost. @@ -337,11 +337,11 @@ Here are some highlights: Best Practices: -- When creating a new WORKER in the `master.cfg` file, leave a comment specifying the server and user account that this WORKER is called from. (At this time, taler.net is the only server used by this implementation, but it's still good practice.) +- When creating a new WORKER in the ``master.cfg`` file, leave a comment specifying the server and user account that this WORKER is called from. (At this time, taler.net is the only server used by this implementation, but it's still good practice.) -- Create a worker from a shell account with this command: `buildbot-worker create-worker <workername> localhost <username> <password>` +- Create a worker from a shell account with this command: ``buildbot-worker create-worker <workername> localhost <username> <password>`` -Then make sure there is a WORKER defined in master.cfg like: `worker.Worker("<username>", "<password>")`` +Then make sure there is a WORKER defined in master.cfg like: ``worker.Worker("<username>", "<password>")`` Documentation Builder --------------------- @@ -667,10 +667,10 @@ What follows is a sort of Wizard. You can find detailed docs at https://docs.we Under *https://weblate.taler.net/create/component/vcs/*: -* **Source code repository** - Generally `git+ssh://git@git.taler.net/<reponame>`. Check with `git remote -v`. +* **Source code repository** - Generally ``git+ssh://git@git.taler.net/<reponame>```. Check with ``git remote -v``. * **Repository branch** - Choose the correct branch to draw from and commit to. -* **Repository push URL** - This is generally `git+ssh://git@git.taler.net/<reponame>` Check with `git remote -v`. -* **Repository browser** - This is the www URL of the Git repo's file browser. Example `https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}` where <repositoryname> gets replaced but *{{filename}}* and other items in braces are actual variables in the string. +* **Repository push URL** - This is generally ``git+ssh://git@git.taler.net/<reponame>``` Check with ``git remote -v``. +* **Repository browser** - This is the www URL of the Git repo's file browser. Example ``https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}`` where ``<repositoryname>`` gets replaced but ``{{filename}}`` and other items in braces are actual variables in the string. * **Merge style** - *Rebase*, in line with GNU Taler development procedures * **Translation license** - *GNU General Public License v3.0 or Later* diff --git a/taler-wallet.rst b/taler-wallet.rst @@ -52,6 +52,11 @@ To use the wallet as a library in your own project, run: $ npm install taler-wallet +Manual withdrawing +================== + +taler-wallet-cli advanced withdraw-manually --exchange https://exchange.eurint.taler.net/ --amount EUR:5 + WebExtension Wallet ===================