[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-deployment] branch master updated: instructions on d
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-deployment] branch master updated: instructions on db reset when deploying to demo |
Date: |
Wed, 18 Oct 2017 15:29:31 +0200 |
This is an automated email from the git hooks/post-receive script.
marcello pushed a commit to branch master
in repository deployment.
The following commit(s) were added to refs/heads/master by this push:
new 19c56e3 instructions on db reset when deploying to demo
19c56e3 is described below
commit 19c56e3ffb6dcfd48388b88fe6a66b5ec83b70f1
Author: Marcello Stanisci <address@hidden>
AuthorDate: Wed Oct 18 15:28:58 2017 +0200
instructions on db reset when deploying to demo
---
doc/onboarding.texi | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index ce9c502..5d14081 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -483,8 +483,11 @@ $ taler-deployment-config-generate
# generate signatures
$ taler-deployment-config-sign
-# upgrade the database! this
-# process depends on the specific version
+# upgrade the database! this process depends on the specific
+# version. However, exchange and merchant have the
+# taler-{exchange,merchant}-dbinit -r command that resets all
+# the tables; the bank might need a tables reset too: refer to
+# django documentation for how to apply migrations to the database.
# generate denomination keys: this is OPTIONAL,
# as the keys under ~/shared-data might be okay
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-deployment] branch master updated: instructions on db reset when deploying to demo,
gnunet <=