I did a thing today.
I deployed a dedicated @ethereum from @ethereumfndn RPC Node on Google Cloud with full logging, metrics and alerts. I configured a single Linux for full computations to deploy two services. Geth, as the execution layer and Lighthouse, as the consensus layer. The combination forms the eth RPC node.
1 reply
1 recast
2 reactions
Making my first ever cast.🥇
I am a DevOps engineer and I will be sharing more about Nodes Deployment and Execution in the coming days.
Do well to follow, let's connect!
0 replies
0 recasts
0 reactions
Top casts
I did a thing today.
I deployed a dedicated @ethereum from @ethereumfndn RPC Node on Google Cloud with full logging, metrics and alerts. I configured a single Linux for full computations to deploy two services. Geth, as the execution layer and Lighthouse, as the consensus layer. The combination forms the eth RPC node.
1 reply
1 recast
2 reactions
@lighthouse with the storage @lighthouse-web3 were integrated to serve as one of the clients that call the execution layer the go-etherum (Geth) which both run in parallel to each other and work together. The Geth helped establish an authrpc endpoint and port for the lighthouse to connect.
1 reply
0 recasts
1 reaction
Making my first ever cast.🥇
I am a DevOps engineer and I will be sharing more about Nodes Deployment and Execution in the coming days.
Do well to follow, let's connect!
0 replies
0 recasts
0 reactions
The endpoints were protected by a simple security token generated and saved locally on the Linux locally, the security provided the route and the execution endpoint to connect to the Geth.