add node v0.10 to travis
This commit is contained in:
parent
2412d014d0
commit
a91b3474e9
@ -1,6 +1,7 @@
|
||||
language: node_js
|
||||
node_js:
|
||||
- 0.8
|
||||
- 0.10
|
||||
before_install:
|
||||
- sudo add-apt-repository --yes ppa:bitcoin/bitcoin
|
||||
- sudo apt-get update
|
||||
|
||||
@ -61,13 +61,14 @@ client.cmd(batch, function(err, address) {
|
||||
See [Enabling SSL on original client](https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon).
|
||||
|
||||
If you're using this to connect to bitcoind across a network it is highly
|
||||
recommended to use SSL, otherwise an attacker may intercept your RPC credentials
|
||||
recommended to enable `ssl`, otherwise an attacker may intercept your RPC credentials
|
||||
resulting in theft of your Bitcoins.
|
||||
|
||||
When enabling `ssl` by setting the configuration option to `true`, the `sslStrict`
|
||||
option will also be enabled by default. It is highly recommended to specify the
|
||||
CA as well to ensure you are not connecting to an attacker's bitcoind attempting
|
||||
to impersonate your own bitcoind.
|
||||
option (verifies the server certificate) will also be enabled by default. It is
|
||||
highly recommended to specify the `sslCa` as well, even if your bitcoind has
|
||||
a certificate signed by an actual CA, to ensure you are connecting
|
||||
to your own bitcoind.
|
||||
|
||||
```js
|
||||
var client = new bitcoin.Client({
|
||||
|
||||
@ -24,7 +24,7 @@
|
||||
"url": "git://github.com/freewil/node-bitcoin.git"
|
||||
},
|
||||
"engines": {
|
||||
"node": "0.8.x"
|
||||
"node": ">= 0.8.0"
|
||||
},
|
||||
"scripts": {
|
||||
"test": "make test"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user