In last 7 days, Ubuntu 18.10 was released followed by release of long awaited Linux kernel 4.19, and last but not least Linus Torvalds is back in drivers seat of Linux development. With this said, it was time to revisit how well does Linux work on MacBook Pro.
Last remaster I did was done on Ubuntu 18.04 with 4.17.6 kernel, I was so underwhelmed that I didn’t even make an “official release”. I was putting all my hopes in kernel 4.19, so now that it’s here, what’s the situation?
Ubuntu 18.10 (4.19 linux kernel) image release for MacBook Pro with Touch Bar
more “Ubuntu 18.10 (4.19 linux kernel) for MacBook Pro”
My post about remastering Ubuntu 18.04 version for MacBook Pro 2017 with Touch Bar working out of box got a lot more attention then I thought it would. This was most notable on Google+ and now I see there are even Reddit posts about it.
If you boot Ubuntu on Macbook Pro 2016/2017 edition model with Touch Bar on Ubuntu 18.04. Not a lot will be working out of box. Basically you’ll only get video working, while important components such as keyboard/touchpad/touch bar/WiFi will not be working.
more “Ubuntu 18.04 image release for MacBook Pro 2017/6 with Touch Bar”
From security reasons, over feature requests, to announcement that Chrome 68 will render all HTTP sites as “not secure” in beginning of July … it’s obvious this is where the web is heading and it had to be done.
For HTTPS encryption, my obvious choice was Let’s Encrypt which I wrote about in past, so without further ado let’s get right to it.
containerized-wordpress-project: Let’s Encrypt update
Few months ago I launched containerized-wordpress-project which let’s you “automagically deploy & run containerized WordPress (PHP7 FPM, Nginx, MariaDB)”.
In latest update I’ve added support for Let’s Encrypt which allows you to have HTTPS encrypted sites/blogs out of box.
I rewrote Nginx container image deployment which now relies on https-portal. Result is updated containerized-wordpress Ansible role whose major updates are to its Docker Compose file as well as deployment of Let’s Encrypt enabled Nginx configs.
For existing sites HTTPS integration is seamless, every HTTP link is automatically redirected to its HTTPS counterpart and certificates will be renewed automatically.
more “Automated way of getting Let’s Encrypt certificates for WordPress using Docker + Ansible”
I’ve been using IRC since late 1990’s, and I continue to do so to this day due to it (still) being one of the driving development forces in various open source communities. Especially in Linux development … and some of my acquintances I can only get in touch with via IRC :)
On my Synology NAS I run ZNC (IRC bouncer/proxy) to which I connect using various IRC clients (irssi/XChat Azure/AndChat) from various platforms (Linux/Mac/Android). In this case ZNC serves as a gateway and no matter which device/client I connect from, I’m always connected to same IRC servers/chat rooms/settings when I left off.
This is all fine and dandy, but connecting from external networks to ZNC means you will hand in your ZNC credentials in plain text. Which is a problem for me, even thought we’re “only” talking about IRC bouncer/proxy.
With that said, how do we encrypt external traffic to our ZNC?
more “Secure traffic to ZNC on Synology with Let’s Encrypt”
Update: containerized-wordpress-project comes with enabled HTTPS site encryption using Let’s Encrypt certificates.
In this blog post, I’ve described what started as simple migration of WordPress blog to AWS, ended up as automation project consisting of publishing multiple Ansible roles deploying and running multiple Docker images.
If you’re not interested in reading about my entire journey, cognition gains and how this process came to be, please skim down to “Birth of: containerized-wordpress-project (TL;DR)” section.
Migrating WordPress blog to AWS (EC2, Lightsail?)
Since I’ve been sold on Amazon’s AWS idea of cloud computing “services” for couple of years now. I’ve wanted, and been trying to migrate this (WordPress) blog to AWS, but somehow it never worked out.
Moving it to EC2 instance, with its own ELB volumes, AMI, EIP, Security Group … it just seemed as an overkill.
When AWS Lightsail was first released, it seemed that was an answer to all my problems.
But it wasn’t, disregarding its bit restrictive/dumbed down versions of original features. Living in Amsterdam, my main problem with it was that it was only available in a single US region.
more “Automagically deploy & run containerized WordPress (PHP7 FPM, Nginx, MariaDB) using Ansible + Docker on AWS”