How to setup a privatenet?

[vncoelho]

Hi @comountainclimber, we would like to already integrate neo-3-preview to neocompiler-eco-3-preview.

In this sense, one of the ingredients we need is to setup the nodes to point to us localhost nodes or the shared-private-net nodes.

[comountainclimber]

Pinging @hal0x2328... This is definitely something we want to support in the near future

[hal0x2328]

We are working toward integrating the explorer code into a Neo3 version of neo-local so everything is pre-configured and Dockerized. For now you could just set it up manually.

You just need to host the front-end code somewhere then install the Lambda functions here using serverless:

https://github.com/CityOfZion/neo3-explorer-api

Then run your Neo3 privatenet node with this plugin installed:

https://github.com/CityOfZion/neo-plugins-coz/tree/master/DynamoDBPublisher

Just need to have stored AWS credentials available for both processes to read (or appropriate IAM roles assigned to a hosting EC2 instance) and it will be up and running in no time, point the front-end at the REST URL and everything should be up and running.

[vncoelho]

@hal0x2328, this is quite complex to me right now....aheuahueaea

I do not understand these Lambda functions.

Off topic:
"I see several plugins here: https://github.com/CityOfZion/neo-plugins-coz
Nice job! @hal0x2328
In my option, as I already told you, your plugins have plenty of space in the official repo.
That would be good for attracting more people to use them and also help in the maintenance."

I will try to learn these setups with AWS asap.
You are all good on servers and high performance application. Congratulations!
I am not expert on this, however, I believe you are all doing a good choice.

Thanks for the guidelines.

[comountainclimber]

I set up the project so that the all application API requests can be configured on one line:

https://github.com/CityOfZion/neo-3-preview/blob/master/src/constants.js#L25

☝️ If the url of the privatenet API is set up it can just be plugged in on this line

[vncoelho]

great, @comountainclimber.
If there is something I can help to try to create a dockerfile for initializing the neo3-explorer-api let me know.

Because the part of the plugin DynamoDBPublisher looks good to me, @hal0x2328. I can include this among the nodes.
However, when running multiple nodes, let's say, 5? How can all of them provide information to the neo3-explorer-api?

[vncoelho]

@comountainclimber, I have been studying the AWS dynamo and Lambda.

I see that it was great that you made that configuration in 1 line.

• on the AWS it will distribute the load upon the requests of the neo3preview users.
• if this API is now provided by Native NEO-NODE, how this load will be distributed?

I also saw this project that may be useful: https://github.com/lambci/docker-lambda