API Servers for Wallet

[abit]

I have set up a wallet/faucet server with ssl. it is at dele-puppy.com  It is currently usable.  Please feel free to test.

I will still need to set up automatic renewal of my ssl certificates, and change the account the wallet is pulling from, but it can be used now. 

I set this wallet/faucet up more as a learning experience than anything else, but if there is a need for it, I can keep it up and updated. 

Please let me know if anything is not working as intended.  It is running todays wallet upgrade.

Thanks for the contribution.
So full URL is wss://dele-puppy.com/ws ?

//Update: it works for me.

//Update 2: pull request submitted https://github.com/cryptonomex/graphene-ui/pull/729

[puppies]

that machine is a little overkill .. it could house 5 witness nodes

That's a fraction of a fraction of our infrastructure
Is there a financial incentive for hosting the nodes?
Documentation ?

No financial benefits.
http://docs.bitshares.eu/bitshares/tutorials/full-node-usage.html

I have not yet read into hosting a SSL secured node but that might come eventually ..

https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-14-04 free and easy
Adding ssl was super easy.  I used

[puppies]

I have set up a wallet/faucet server with ssl.  it is at dele-puppy.com  It is currently usable.  Please feel free to test.

I will still need to set up automatic renewal of my ssl certificates, and change the account the wallet is pulling from, but it can be used now. 

I set this wallet/faucet up more as a learning experience than anything else, but if there is a need for it, I can keep it up and updated. 

Please let me know if anything is not working as intended.  It is running todays wallet upgrade.

[xeroc]

that machine is a little overkill .. it could house 5 witness nodes

That's a fraction of a fraction of our infrastructure
Is there a financial incentive for hosting the nodes?
Documentation ?

No financial benefits.
http://docs.bitshares.eu/bitshares/tutorials/full-node-usage.html

I have not yet read into hosting a SSL secured node but that might come eventually ..

[Xypher]

that machine is a little overkill .. it could house 5 witness nodes

That's a fraction of a fraction of our infrastructure
Is there a financial incentive for hosting the nodes?
Documentation ?

[betax]

i think it will be as simple as to pass the different params for docker.

[betax]

Could this be done as a deployment package in Azure? Both Faucet an API. (Thinking of killing 2 birds).

Never worked with Azure, but this can certainly be done with docker ..

We were talking about demonstrating something to Azure as a chain which can hosted there, obviously they also support docker.

This is the Ethereum Blockapps Strato raw template https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/blockapps-strato/azuredeploy.json
here is the main deployment  https://azure.microsoft.com/en-us/documentation/templates/blockapps-strato/
where is published https://azure.microsoft.com/en-us/documentation/templates/
and the contact https://azure.microsoft.com/en-gb/blog/ethereum-blockchain-as-a-service-now-on-azure/

[xeroc]

that machine is a little overkill .. it could house 5 witness nodes

[Xypher]

We had offered an i7, 32gb ram , 10 tb bandwidth, 100 mbps server to a project at the nxt community for approx 450 USD (1/3rd of retail rate) - but they didn't need it.
If needed, am open to offering it for this. We can also have more servers deployed from our infrastructure at a highly subsidized rate.

Regards

[xeroc]

Could this be done as a deployment package in Azure? Both Faucet an API. (Thinking of killing 2 birds).

Never worked with Azure, but this can certainly be done with docker ..

[betax]

Could this be done as a deployment package in Azure? Both Faucet an API. (Thinking of killing 2 birds).

[merivercap]

We are looking for more redundancy in the API servers that can be integrated into the default wallet.  Currently we have bitshares.openledger.info and bitshares.dacplay.org.  To prevent/minimize downtime in the event of a server failure we would like to see additional API servers available.

Also we would like to see additional faucets set up and running.  The faucets have control over the referral program.   We will integrate the faucet / API servers into the default light wallet client.  This way the user can quickly and easily switch.

All that is required is a domain name and vetting by this community.

In addition: need a SSL/TLS certificate so it can serve secure connections:
need to use wss://youdomain.com/ws but not ws://youdomain.com/ws.

We've ever had 3 more API servers, but all of them don't support secure connections, so at the end we can't use them.

BTW what do you guys think of Let's Encrypt for SSL?: https://letsencrypt.org/

We should have a faucet available to use soon.. we currently have the Graphene wallet running until we get our wallet ready.

[puppies]

I'm working on setting up a faucet but am running into an issue
https://bitsharestalk.org/index.php/topic,21311.0.html
Seems to be the same problem from
https://github.com/cryptonomex/faucet/issues/1

Any help on what I am doing wrong would be appreciated

[karnal]

BM,

I'd like to get a few running myself, however see https://github.com/cryptonomex/graphene/issues/522

The network is probably 100% Linux right now, some diversity might be helpful.

p.s: No point in even trying with boost <= 1.6 right? (open and freebsd have <1.6 right now)

[abit]

We are looking for more redundancy in the API servers that can be integrated into the default wallet.  Currently we have bitshares.openledger.info and bitshares.dacplay.org.  To prevent/minimize downtime in the event of a server failure we would like to see additional API servers available.

Also we would like to see additional faucets set up and running.  The faucets have control over the referral program.   We will integrate the faucet / API servers into the default light wallet client.  This way the user can quickly and easily switch.

All that is required is a domain name and vetting by this community.

In addition: need a SSL/TLS certificate so it can serve secure connections:
need to use wss://youdomain.com/ws but not ws://youdomain.com/ws.

We've ever had 3 more API servers, but all of them don't support secure connections, so at the end we can't use them.