0 Comments

As I’ve blogged a while ago (july 2019), I made my pi a docker host. I used a pi 3, but moved now to a pi 4 with ubuntu as host.

If you want to know how I did it, my collegeau Johan explains it on his blog How to install Ubuntu on a Raspberry PI – Johan the Developer and the followup How to install Docker on a Raspberry PI – Johan the Developer

Once you have that in place, you can proceed to get a Nebl Docker container.

The Nebl Docker container

I found this official one on dockerhub neblioteam/nebliod-rpi (docker.com)

The instructions are always clear at dockerhub. Step 1 is to get the image:

docker pull neblioteam/nebliod-rpi

Step 2 is to use the image to run a container:

sudo docker run -d --restart=always --name nebliod -v $HOME/neblio-data:/root/.neblio -p 6325:6325 neblioteam/nebliod-rpi


If you are less familiar with Docker, this does mount the folder /root/.neblio in your container to the folder on your docker host at the home or ~ and then neblio-data. This contains your wallet which password is generated at the 1st start of the container.


Use the container

I started a shell in the container, so it will save me some typing:

sudo docker exec -it nebliod bash

you can get your wallet address with this command:

nebliod listreceivedbyaddress 0 true


If you would not start bash first, but just run it from your docker host:

sudo docker exec -it nebliod nebliod listreceivedbyaddress 0 true


You can see that the password is random on line 16 here

docker-nebliod/neblio_init at master · NeblioTeam/docker-nebliod (github.com)

You should transfer Nebl to your wallet. It will take 24 hours to mature. Then the weight will gain for staking.

Run the nebliod getstakeinginfo to see the weight, if the coins are mature and the expectedtime in seconds for staking.

You can also use nebliod getbalance to just get the balance from your wallet without the address and confirmations which the listreceivedbyaddress returns.

So it’s all up and running 24/7 on my Raspberry Pi 4. Now it’s just a matter of time before I will receive the first stake.


If you want to know more about Neblio, please check out their website at Neblio - Blockchain. Simplified.


Good luck! I hope it’s helpful

Post on LinkedIn
0 Comments

When you have a nice .Net core solution and want to see the code smell and technical debt, you can analyze it with SonarCube

SonarQube

I started by browsing to the docker hub and used a container:

docker pull sonarqube

docker run -d --name sonarqube -p 9000:9000 sonarqube

The default username is ‘admin’ and the default password is ‘admin’ so once it is started you can head over to http://localhost:9000 and login. Configure your project there and copy the key/hash

You can get the SonarLint extension for Visual Studio and Visual Studio Code and link it to the local SonarCube server.

You need this one time installation of a global tool:

dotnet tool install --global dotnet-sonarscanner --version 4.3.1

And then:

dotnet sonarscanner begin /k:"project-key" 
dotnet build <path to solution.sln>
dotnet sonarscanner end 

Wait a minute after it finishes so that the SonarCube server has some time to process the results. Check the dashboard again to see the smell, bugs and tech debt. This does help you verify if you are still coding SOLID.


Happy coding!

Post on LinkedIn

Recently the Raspberry Pi 4 was announced, But I am currently using my rpi 3test_1 and want to run Rabbit MQ on it in Docker. So I used these two commands to get it to work and I just wanted to share it:


sudo rm /etc/apt/sources.list.d/docker.list;

curl –sL get.docker.com | sed ‘s/9)/10)’ | sh

If you would like to use Docker as a non-root user you should add your user to the docker group:

sudo usermod –aG docker pi

To get Rabbit MQ (which has arm container) on the pi with a management web interface run:

sudo docker run –d –hostname my-rabbit –name some-rabbit –p 15672:15672 –p 5672:5672 rabbitmq:3-management

Then get the ip of the docker container with (but since you added the ports in the previous command, this step can be skipped):

sudo docker inspect –f ‘{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}’ some-rabbit

Then you can launch a browser and go to http://thatipaddress:15672 and login with 'guest/guest'. If you did not lookup the ip of the container you can use the ip of the pi because you opened container ports when running it.


8850828555_df7c7bd300_b


Good luck!

Post on LinkedIn