, we created an AWS account, deployed an EC2 Linux instance and learned how to SSH into that server. With the help of Docker, we’ll deploy a private NEO within the linux AMI we’ve just created! Last week network So what is ? Docker is containerization — it helps us run an “image” or package, where we don’t have to worry about the NEO nodes, network, dependencies and any pre-configurations. It is all written out for us as a docker image, all we need to do is download and run it! Docker technology Lets, though, take a moment to understand our particular Docker image. It contains 4 , the minimum required to bring up a working NEO network, communicating internally via ports 30333-30336 TCP. We will then expose the (20331–20334) to the outside world by manipulating our AWS security group. NEO consensus nodes communication ports testNet Check out the , an open-source community in partnership with NEO. This is their Docker image , for those of you who want to check it out! Citizen of Zion source code After entering your Amazon Linux instance via secure shell, we will install Docker … Install Docker Step 1: sudo yum update -ysudo yum install -y dockersudo service docker startsudo usermod -a -G docker ec2-user Check and deploy our Docker NEO network image Step 2: docker info #just a checkdocker pull cityofzion/neo-privatenet docker run --rm -d --name neo-privatenet --expose=20331-20334 --expose=30333-30336 -p 20333-20336:20333-20336/tcp -p 30333-30336:30333-30336/tcp cityofzion/neo-privatenet Check that your image is running! docker ps Adding port 30331–30334 to your security group Step 3: Log onto the AWS console, > Under , click . Click on the security group assigned to your instance. Create the following rules: Services EC2. NETWORK & SECURITY Security Groups Edit inbound *These rules apply immediately! Connect from your ! Step 4: neo-prompt Open command prompt on local: ubuntusudo -i cd <location of neo-python>source venv/bin/activate Remember how we made note of the public IP in the last article? Let’s use that here: np-prompt -p <server IP> Great! we are done! : Restarting the NEO block-chain. Bonus command From our experience, due to server memory constraints, your image will need to be whipped and restarted weekly. The command to do so is as follows: docker stop neo-privatenet Then use the following on your own np-prompt (Ubuntu): rm -rf /root/.neopython/Chains/ As usual, I’ll give my project a shout out: is a marketing platform for local business, generating engagement through small activities and rewarding users with cryptocurrency they can later spend on these stores. Check us out and give us your feedback on and ! Nodis.io Instagram Facebook Deploying a NEP-5 smart contract (part 1) Next week’s guide:

Too Long; Didn't Read

Making security fun one episode at a time

Building your private NEO network on AWS (part 2)

Too Long; Didn't Read

Dominic Fung

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Building your private NEO network on AWS (part 2)

Too Long; Didn't Read

Dominic Fung

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES