If you’ve been tinkering with a Raspberry Pi for a while, chances are you’ve hit this annoying wall: your Pi just won’t boot anymore. No screen. No OS. No mercy. Most of the time? It’s the SD card playing dead.
Don’t panic. It’s often not fatal. In many cases, your SD card just has a corrupted file system — and that, my friend, can be fixed.
So one day you’re halfway through your morning coffee, and someone has already left you a message:
ext4-fs error: unable to read superblock
The system won’t boot. Files are completely inaccessible. There’s no obvious way to move forward. Looks like you’ve got a full-blown mess on your hands, and you’ve got no clue where it even started.
Alright, first things first—breathe. This can be fixed. Grab that coffee — and let’s clean up this mess fast!
Continue readingImagine this scenario: you need to practice old-school PHP + MySQL and you have to setup a practice environment.
The first choice is almost obvious (and normally mentioned everywhere), that is installing a local LAMP/MAMP/WAMPP instance so you can have a local Apache server with PHP and MySQL.
But what if you don’t want (or can’t) install that? Well, another obvious option is to use any of the thousands hostings that for a fee, will provide you a working environment, with everything ready to use to host your “apps”.
But what if you want more control? Well, you could use Docker on your own machine and have everything accesible. But, again, another constraint: what if you need to access from anywhere and you don’t want to expose your home or work environment to the Internet…? And what if you don’t want Docker to be in background consuming your resources…?
Continue reading