From bb049d4f2b5d79b1ad5af5f1bcad6ce32103a7b7 Mon Sep 17 00:00:00 2001 From: perseus-algol <129220578+perseus-algol@users.noreply.github.com> Date: Tue, 16 Apr 2024 02:25:38 +0300 Subject: [PATCH] [docs] Fix list formatting in basics.md (#1758) --- docs/basics.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/basics.md b/docs/basics.md index 52cb0dff5..180ef2dba 100644 --- a/docs/basics.md +++ b/docs/basics.md @@ -7,10 +7,10 @@ The architecture for various components are already described at [docs.cardano.o While we do not intend to hand out step-by-step instructions, the tools are often misused as a shortcut to avoid ensuring base skillsets mentioned on home page. Some of the common gotchas that we often find SPOs to miss out on: - - It is imperative that pools operate with highly accurate system time, in order to propogate blocks to network in a timely manner and avoid penalties to own (or at times other competing) blocks. Please refer to sample guidance [here ](https://ubuntu.com/server/docs/network-ntp) for details - the precise steps may depend on your OS. - - Ensure your Firewall rules at Network as well as OS level are updated according to the usage of your system, you'd want to whitelist the rules that you really need to open to world (eg: You might need node, SSH, and potentially secured webserver/proxy ports to be open, depending on components you run). - - Update your SSH Configuration to prevent password-based logon. - - Ensure that you use offline workflow, you should never require to have your offline keys on online nodes. The tools provide you backup/restore functionality to only pass online keys to online nodes. +- It is imperative that pools operate with highly accurate system time, in order to propogate blocks to network in a timely manner and avoid penalties to own (or at times other competing) blocks. Please refer to sample guidance [here ](https://ubuntu.com/server/docs/network-ntp) for details - the precise steps may depend on your OS. +- Ensure your Firewall rules at Network as well as OS level are updated according to the usage of your system, you'd want to whitelist the rules that you really need to open to world (eg: You might need node, SSH, and potentially secured webserver/proxy ports to be open, depending on components you run). +- Update your SSH Configuration to prevent password-based logon. +- Ensure that you use offline workflow, you should never require to have your offline keys on online nodes. The tools provide you backup/restore functionality to only pass online keys to online nodes. #### Pre-Requisites