phahulin

I think it's a good idea and will simplify things for end-users. > As soon as the new release is tagged, the image produced as part of the latest PR...

It looks like address auto-correction changed ZIP code from `98109` to `98109-3517`. @shkron do you happen to know if it's the correct zip+4 code? Maybe you have a postoffice box...

To avoid exceptions, I'd propose to update playbooks to add this prefix on every network, so also `core-bootnodes.txt`, `core-spec.json`. This can also be joined with https://github.com/poanetwork/wiki/issues/22 by moving toml files...

Yes, I guess we'll need another poa-devops playbook to update files on existing nodes

@6proof which "another minor issue" do you mean?

If a user can create a server and setup access via ssh keys, hopefully it won't be too confusing for him. So probably add an optional step for a case...

Added checkboxes, @hashguide please check them complete as you go

Both can be used interchangeably http://docs.ansible.com/ansible/latest/ansible-playbook.html#cmdoption-ansible-playbook-private-key

You mean these two guides, right? https://github.com/poanetwork/wiki/wiki/Validator-Node-Non-AWS https://github.com/poanetwork/wiki/wiki/Bootnode-Setup-Non-AWS In the first guide in "Configure node with Deployment-playbook" section in 7th paragraph "set values given to you by Master of Ceremony..."...

I don't think there was a strong reason, we probably based our spec on kovan's.