Deploying Blockscout
Deployment with Terraform 12 is unstable due to these bugs: #144, #147, #148, #149. Please use TF 11.11 - 11.14 and following branch for deployment https://github.com/poanetwork/blockscout-terraform/tree/before-t12
If you are not using a Mac, skip to step 1 below.
Mac Users Only
To avoid the following error (which results in a Python crash):
TASK [main_software : Fetch environment variables] ************************************
objc[12816]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[12816]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Open terminal:
nano .bash_profileAdd the following line to the end of the file:
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESSave, exit, close terminal and re-open the terminal. Check to see that the environment variable is now set:
env
1) Ensure all BlockScout prerequisites are installed with the correct version number
2) Create the AWS access key and secret access key for user with sufficient permissions;
3) Create hosts file from hosts.example (mv hosts.example hosts) and adjust to your needs. Each host should represent each BlockScout instance you want to deploy.
Each host name should belong exactly to one group. Also, as per Ansible requirements, hosts and group names should be unique.
The simplest hosts file with one BlockScout instance will look like:
Where [group] is a group name, which will be interpreted as a prefix for all created resources and host is a name of BlockScout instance.
4) For each host merge blockscout.yml.example and all.yml.example config template files in host_vars folder into single config file with the same name as in hosts file:
If you have already merged infrastructure.yml.example and all.yml while deploying the BlockScout infrastructure, you can simply add the blockscout.yml.example to the merged file: cat host_vars/blockscout.yml.example >> host_vars/host.yml
5) For each group merge blockscout.yml.example and all.yml.example config template files in group_vars folder into single config file with the same name as group name in hosts file:
If you have already merged infrastructure.yml.example and all.yml while deploying the BlockScout infrastructure, you can simply add the blockscout.yml.example to the merged file: cat group_vars/blockscout.yml.example >> group_vars/host.yml
6) Adjust the variables at group_vars and host_vars.
You can move variables between host and group vars depending on if variable should be applied to the host or to the entire group.
Also, if you need to distribute variables across all the hosts/groups, you can add these variables to the group_vars/all.yml file.
More on variable precedence => Official Ansible Docs.
7) Run ansible-playbook deploy_software.yml
8) When the prompt appears, check that server is running and there is no visual artifacts. The server will be launched at port 4000 at the same machine where you run the Ansible playbooks. If you face any errors you can either fix it or cancel the deployment by pressing Ctrl+C and then pressing A when additionally prompted.
9) When the server is ready to be deployed simply press enter and deployer will upload Blockscout to the appropriate S3.
10) Two other prompts will appear to ensure your will on updating the Parameter Store variables and deploying the BlockScout through the CodeDeploy. Both yes and true will be interpreted as the confirmation.
11) (optional) If the deployment fails, you can use the following tags to repeat the particular steps of the deployment:
build
update_vars
deploy
12) Monitor and manage your deployment at CodeDeploy service page at AWS Console.
Last updated
