You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -32,22 +31,22 @@ If Web-Wallet is not running locally, https is the default protocol. To set up
32
31
33
32
## Configuring:
34
33
35
-
Configure the database connection parameters, localizations and features of Web-Wallet by copying 'settings.json.template' to 'settings.json' and making your changes in 'settings.json'.
34
+
Configure the database connection parameters, localizations and features of YourApp by copying 'settings.json.template' to 'settings.json' and making your changes in 'settings.json'.
36
35
37
-
Configure Web-Wallet and daemon for local or non-local operation, or a combination of both. For instance:
36
+
Configure YourApp and daemon for local or non-local operation, or a combination of both. For instance:
38
37
39
-
If the coin daemon is running on the same machine as Web-Wallet, the daemon's config file will be used. It can be found at:
38
+
If the coin daemon is running on the same machine as YourApp, the daemon's config file will be used. It can be found at:
(Substitute your coin's name for 'SpaceCredits' above.)
49
+
(Substitute your coin's name for 'YourCoin' above.)
51
50
52
51
If the daemon is running on another machine, you will need to configure node.js's coin.conf file to match the daemon's config file. coin.conf is found in: lib/coin.conf
53
52
@@ -61,43 +60,43 @@ Either way, the config file will need at a minimum the following parameters:
61
60
62
61
Local vs Not-Local configuration:
63
62
64
-
The config file parameter 'rpcconnect' determines whether the daemon (and thus Web-Wallet) is local or not-local, even if the daemon and Web-Wallet are both running on the same machine. Web-Wallet's boolean flag 'isLocal' is determined to be true if 'rpcconnect' is one of the following:
63
+
The config file parameter 'rpcconnect' determines whether the daemon is local or not-local, even if the daemon and YourApp are both running on the same machine. YourApp's boolean flag 'isLocal' is determined to be true if 'rpcconnect' is one of the following:
65
64
66
65
> rpcconnect=127.0.0.1
67
66
> rpcconnect=localhost
68
67
> rpcconnect=192.168.x.x
69
68
> rpcconnect=hostname_with_no_tld
70
69
71
-
The last two examples allow for Web-Wallet to be considered 'local', even though the node and daemon may be running on different machines on the same local network.
70
+
The last two examples allow for YourApp to be considered 'local', even though the node and daemon may be running on different machines on the same local network.
72
71
73
-
If the daemon and Web-Wallet are both running on the same machine, you can still define Web-Wallet as NOT-local by setting the 'rpcconnect' parameter to a fully qualified domain name (i.e. myhost.homelan.net), which requirs a simple modification to the machine's hosts file. (e.g. 192.168.1.246 myhost.homelan.net)
72
+
If the daemon and YourApp are both running on the same machine, you can still define YourApp as NOT-local by setting the 'rpcconnect' parameter to a fully qualified domain name (i.e. myhost.homelan.net), which requirs a simple modification to the machine's hosts file. (e.g. 192.168.1.246 myhost.homelan.net)
74
73
75
-
If 'isLocal' is true, more control over Web-Wallet is allowed. (i.e. encrypting the wallet, locking/unlocking the wallet for sending/staking, and more wallet stats and features are available.)
74
+
If 'isLocal' is true, more control over YourApp is allowed. (i.e. encrypting the wallet, locking/unlocking the wallet for sending/staking, and more wallet stats and features are available.)
76
75
77
76
[See 'rpcconnect' in the coin's source code, init.cpp, for more information.]
78
77
79
-
If you need to run Web-Wallet app from a "sub directory" of the main web-site (e.g. https://example.com/wallet/), change the settings.json parameter, chRoot to: "".
78
+
If you need to run YourApp app from a "sub directory" of the main web-site (e.g. https://example.com/wallet/), change the settings.json parameter, chRoot to: "".
80
79
81
80
82
81
## Running:
83
82
84
83
Windows:
85
84
86
-
> web-wallet.bat
85
+
> YourApp.bat
87
86
88
87
(If supervisor is not installed, run 'npm install supervisor'.)
89
88
90
89
Linux:
91
90
92
-
> web-wallet.sh
91
+
> YourApp.sh
93
92
94
93
(If 'daemon' is not installed, please consult your Linux distro's documentation for installing 'daemon'.)
95
94
96
-
Web-Wallet has an admin account pre-defined which you can login with:
95
+
YourApp has an admin account pre-defined which you can login with:
97
96
98
97
> Login: MASTER_ACCOUNT
99
98
> Password: password (you will be required to change this)
100
99
101
-
The MASTER_ACOUNT always sees Web-Wallet as 'local' and has views into the wallet as if you were running a Qt wallet (i.e. the full wallet balance).
100
+
The MASTER_ACOUNT always sees YourApp as 'local' and has views into the wallet as if you were running a Qt wallet (i.e. the full wallet balance).
102
101
103
-
To setup individual accounts, use Web-Wallet's Signup page, or login with a social media account.
102
+
To setup individual accounts, use YourApp's Signup page, or login with a social media account.
0 commit comments