Il passaggio dalla teoria alla pratica dà sempre le sue soddisfazioni :) 

Note:Pantahub is the only place where Linux firmware can be shared and deployed for any device, You can signup @pantahub here:http://www.pantahub.com

Make your RPI3 device ready to deploy Laravel 7.12.0 by following 6 Steps

Step 1: Burn the RPI3 initial stable image into your sd card.

a) Download RPI3 image

Click to download

b) unxz the device image

Run $ unxz rpi3_initial_stable.img.xz

c) Burn image into sd card using Raspberry Pi Imager 1.2

Step 2: Boot your RPI3

a) Insert your sd card and supply the power

Step 3: Singup @pantahub here http://www.pantahub.com

Step 4: Download & Install a CLI tool “pvr”

Note: pvr is a CLI tool which can be used to interact with your device through pantahub platform. Note: Using pvr you can share your firmware and projects as simple as with a git tree: Note: Move the pvr binary to your bin folder after download.

Linux(AMD64): Download Linux(ARM32v6): Download Darwin(AMD64): Download

pvr clone; pvr commit; pvr post

To install from github source code:

$ go get gitlab.com/pantacor/pvr $ go build -o ~/bin/pvr gitlab.com/pantacor/pvr

Note: You need “GOLANG” to be installed in your system for building pvr from github source code.

Step 5: Detect & Claim your device

a) Connect a LAN cable between your RPI3 & computer/Router.

b) Open your terminal & run $ pvr scan

c) Claim your device

$ pvr claim -c merely-regular-gorilla https://api.pantahub.com:443/devices/5f1b9c44e193a5000afa9901

d) Log into Panthub.com and check whether the newly claimed device appeared in the dashboard or not.

Step 6: Clone the device to your computer using the Clone URL of your device

$ pvr clone https://pvr.pantahub.com/sirinibin/presently_learning_pelican/0 presently_learning_pelican

Now your device is ready to deploy your Laravel 7.12.0 app

Deploy your Laravel 7.12.0 app to the device by following 5 Steps

Step 1: Move to device root dir

`$ cd presently_learning_pelican`

Step 2: Add a new app “laravel” into the device

sirinibin/arm32v7-laravel-7.12.0:latest is a Docker image made for the devices with ARM32 architecture

You can customise the docker image for your custom Laravel app.

$ pvr app add laravel --from=sirinibin/arm32v7-laravel-7.12.0latest

Step 3: Deploy the changes to the device

$ pvr add . $ pvr commit $ pvr post

Step 4: Check the device status changes in Pantahub.com dashboard & wait for the status to become "DONE"

Status 1:

Status 2:

Status 3:

Status 4:

Step 5: Verify the “laravel” app deployment

Access the device IP: http://10.42.0.231 in your web browser.

Note:Pantahub is the only place where Linux firmware can be shared and deployed for any device, You can signup @pantahub here:http://www.pantahub.com

Make your RPI3 device ready to deploy Yii2 by following 6 Steps

Step 1: Burn the RPI3 initial stable image into your sd card.

a) Download RPI3 image

Click to download: https://pantavisor-ci.s3.amazonaws.com/pv-initial-devices/tags/012-rc2/162943661/rpi3_initial_stable.img.xz

b) unxz the device image

Run $ unxz rpi3_initial_stable.img.xz

c) Burn image into sd card using Raspberry Pi Imager 1.2

Step 2: Boot your RPI3

a) Insert your sd card and supply the power

Step 3: Singup @pantahub here http://www.pantahub.com

Step 4: Download & Install a CLI tool “pvr”

Note: pvr is a CLI tool which can be used to interact with your device through pantahub platform. Note: Using pvr you can share your firmware and projects as simple as with a git tree: pvr clone; pvr commit; pvr post

$ go get gitlab.com/pantacor/pvr $ go build -o ~/bin/pvr gitlab.com/pantacor/pvr

Note: You need “GOLANG” to be installed in your system for building pvr from source code.

Step 5: Detect & Claim your device

a) Connect a LAN cable between your RPI3 & computer/Router.

b) Open your terminal & run $ pvr scan

c) Claim your device

$ pvr claim -c merely-regular-gorilla https://api.pantahub.com:443/devices/5f1b9c44e193a5000afa9901

d) Log into Panthub.com and check whether the newly claimed device appeared in the dashboard or not.

Step 6: Clone the device to your computer using the Clone URL of your device

$ pvr clone https://pvr.pantahub.com/sirinibin/presently_learning_pelican/0 presently_learning_pelican

Now your device is ready to deploy your Yii2 app

Deploy your Yii2 app to the device by following 5 Steps

Step 1: Move to device root dir

`$ cd presently_learning_pelican`

Step 2: Add a new app “yii2” into the device

sirinibin/yii2-basic-arm32v7:latest is a Docker image made for the devices with ARM32 architecture

You can customise the docker image for your custom Yii2 app.

$ pvr app add yii2 --from=sirinibin/yii2-basic-arm32v7:latest

Step 3: Deploy the changes to the device

$ pvr add . $ pvr commit $ pvr post

Step 4: Check the device status changes in Pantahub.com dashboard & wait for the status to become "DONE"

Status 1:

Status 2:

Status 3:

Status 4:

Step 5: Verify the “yii2” app deployment

Access the device IP: http://10.42.0.231/myapp1/web/ in your web browser.

Step 1: Add new app “solr” into the device

$ pvr app add solr --from=arm32v7/solr:5-slim

Step 2: Deploy the changes to the device

$ pvr add . $ pvr commit $ pvr post

Step 3: Access the Solr dashboard

http://10.42.0.231:8983/

Step 4: Try creating your 1st Solr Core

a) SSH into the app container “solr”

ssh -p 8222 [email protected]

b) Create a new core

$ cd /opt/solr/bin $ ./solr create -c "core1"

c) Access the Solr core you just created

http://10.42.0.231:8983/solr/#/~cores

Raspberry Pi TV-Out Adventures - Pi2Scart

I’ve been working on getting several Raspberry Pi 3′s hooked up to TVs I use down in the basement for retrogaming.  The advantage in using a CRT is that there’s less lag (button press latency) and you get a more authentic experience.  I grew up playing these games on CRTs and they just feel more natural on there.  The difficulty is that a) the RPI3 only displays HDMI (and not really at a resolution the games were meant to be played at) and b) these TVs only accept composite (gross) or Component (acceptable).

The RPI3 has a series of pins on the side meant for general input/output (GPIO).  I bought several TV output solutions that plug into these (called Pi hats).  This one in particular is a Pi2Scart - which is a project that has a sister project called Pi2Jamma (which is meant for setting up an arcade machine with a RPI driving things).  The difficulty in using these TV output solutions is that you must a) have the resolution set so that you can navigate the game selection menu (I’m using RetroPie) and b) have the emulator set the resolution correctly based on the system you’re playing (otherwise Mario looks really weird for example).  

After trying a stock RetroPie distribution image and researching how to set the config.txt in the boot partition, I ended up using an image out there that already has these resolutions set up.  Needless to say, it’s a godsend here - saving so much time with setting up each emulator.  I’ll get to the other RPI TV out solutions I purchased lately but this one is definitely looking promising now with that image.  I have another linux distribution to try with this as well so there might be an update for that.

Other things worth mentioning in the setup here.  I ended up using a RPI enclosure that’s basically a giant heatsink that is attached the the hottest chips on the board with some thermal pads.  And I overclocked my RPI about 15-25% to get the most I could out of it.  Because of the way the enclosure works with the GPIO pins, I soldered the wires on the little fans (which sit under the PI2Scart with an air gap) to the board directly.  With the heatsink, things get warm but are quite manageable without any freezing or lockups.

I also have this SCART to Component box I bought years back that I’ve pulled out and have used here.  I had to open it up and tweak the pots inside to get the desired color (which admittedly is a little on the cool side).  I also decided to add a small copper heat sink to the voltage regulator with a volt (after drilling a hole through the piece of copper).  I don’t know if that’s really going to help, but that voltage regulator is super hot (it was hot with a 1-amp power brick and still hot with a 300ma one).  I’d love to move to one of Mike Chi’s (RetroTink) RGB2COMP units when I can.

I’ve been toying around with getting the Reicast emulator for the longest time.  As I recently started using the GDEMU clone disc emulator and had to use GDI images for it, I thought this might be a breakthrough (using those instead of CDI images).  But Reicast just refuses to work on this platform - whether using CDI images (which just send you to the title screen) or GDI images (which send you to the system screen and then refuse to play the disc).  I - while I know the Rpi3 is under-powered for Dreamcast emulation - I had hoped it could run some 2D games - maybe just puzzle games.  I also wanted to get this working so that I could share it with a friend - who is more of a Sega enthusiast.

So basically I had to give that up plan and focus back on getting the system in order and then backing it up.. meaning I’ve also been updating the emulators and making a card image.  Besides my own wants here, this is so that I can back it up and send to a friend with a messed-up system.  So I got that done and had a 32gb image of the Micro SD card.  And I ordered another 32gb SD card to make the copy to.  Well.. turns out that not all SD cards are the same.  The card I owned was a little over 32gb and the card I ordered was under.  So the copy software won’t work.

After researching how to address this and running into an overly-complicated brick wall (which would involve a laptop running Linux to work at all), I just pulled a 64gb card out of a device and used it instead.  I’ll be keeping the 64gb card and sending the existing 32gb one to the friend.