Onboarding Blobbers common issues

Here is some feedback relating to the onboarding process.

Static LAN IP:-
If you experience a problem relating to requiring a static LAN IP on your server, community member Da Roux Barrett found a solution by editing the /etc/netplan/*.yaml file as per instructions at https://linuxconfig.org/how-to-configure-static-ip-address-on-ubuntu-18-04-bionic-beaver-linux
Note: most people will not require this, also the indent spacing or tabs in the file have to be exact for it to the work!

Dynamic IP/DNS:-
Fixed IP addresses are recommended because the URL/IP address assigned to a blobber when created cannot be changed. However, if you do not have a permanent fixed IP, you may wish to evaluate the option of using a Dynamic DNS service such as https://www.noip.com/ (there are others). Again, this is not recommended, especially if your IP address changes frequently, but could be viable if it changes infrequently

Restarting Blobber:-
If you need to restart your blobber, due to problems or to implement a configuration change.
docker ps
will list the processes. Identify processes relating to your blobber (there should be 3 - blobber, validator, postgres)
docker kill <proc1> <proc2> <proc3>
You then locate to the blobber directory and start the blobber again

As added to the article, Many commands will require sudo in front of them if you are not logged in as root. This relates to commands that are installing outside of the users home folder. So each of the apt install commands, plus golang and docker installs.

Non-Debian Linux:-
RHEL Linux such as Centos use YUM package manager instead of APT so commands and packages referenced would need to be adapted. However according to community member Chris K it is a little more complicated than that. Apparently, docker has issues in this platform but an alternative podman can be used via an alias. In short, it is best to wait until this has been addressed by the team or use pre-built image instead.

Router setup:-
If you are running through a broadband connection, you will need to set up your router accordingly. There are an many different router models, each with their own administrative interfaces but here is a general description.
You will need to enable port 22 (for SSH access), ports 5051-505x and 5061-506x (default range for 0chain blobber access - x being number of blobbers planned, max 6). You may also require additional ports or configure alternative port mapping it these are already assigned to other computers on your network.
So in your router admin, you will need to:-
a) map each port to the server machine (may be in a list) or IP address.
b) unblock or create rules in your firewall to enable these ports.
c) additionally there may be settings relating to bandwidth limitation on certain ports or connected devices. If so, you could configure this appropriately, so that the server has priority bandwidth.