A meeting about HTTPS on Making WordPress

Wednesday I attended to my first meeting in Making WordPress Slack channel.

It was about HTTPS and there are two goals.

The first one is to look for a way to migrate from an HTTP site without human intervention. The other is about introducing a way to enable HTTPS during installation.

Technicalities apart, what struck me was the tone of the discussions.

There were a handful people talking about a difficult problem to tackle. Even if technical issues were discussed, the focus was on the users. How to make it simple for them to use this feature?

The next time you use an open source software and rejoice about a new feature, think about all the people involved in shipping that particular feature.

Many of them gave their time for free to build that particular thing.

Cover image: “People’s Evening”

A component-based deploy strategy for WP Engine

Deploying to WP Engine, one component at a time.

In the last months at DriveK, I’ve worked a lot with WP Engine.

WP Engine, for those who don’t know, is a managed WordPress hosting company. They have worked hard on their infrastructure performance and security to give a top-notch service.

If you have a WordPress site, just create an install and forget about all those server related issues. It’s all on their side. You only have to think about your application, your themes, and your plugins.

The flip side of this is that the infrastructure is invisible. There is no concept of VPS, server, physical machine, virtual machine and such. And this means (as of January 2016), no SSH access.

That’s where deployment issues arise.

Continue reading “A component-based deploy strategy for WP Engine”

A year in WordCamps

So, it’s the end of the year once again, and we’re all making our year’s balance.

For me, 2015 is the year I turned from an anonymous WordPress developer to an (equally) anonymous WordPress community member.

I’m writing this three weeks after the inaugural WordCamp US in Philadelphia. It’s been (roughly) just one year after my first WordCamp Europe in Sofia. I attended also to WordCamp Europe in Seville and WordCamp Zürich. And, in the middle of that I helped organizing  the WordPress Meetup Milan and the first Italian Contributor Day, back in November.

Now I’m starting to understand what WordPress really is.

I’ve been working with WordPress since 2009, but I’ve never been involved in the community. When you are just user of an open source software, you focus on maximizing  what you could get from the software. When you start being involved in its community, you start to switch focus, thinking about what you could give to the software.

Italian Community at WordCamp US

So you start translating it in your language. You find a typo in the docs and you fix it. You start to take part to discussions. Maybe you’re a developer working with the software as your day job, and you start to contribute with patches, maybe just a single, stupid line. Or you’re a designer, and you help to improve the UI. In short, you show up. And the WordPress community adhere to the old saying:

decisions are made by those who show up

If something makes you feel uncomfortable, just show up and tell. I think that’s really a good way of doing things.


New year’s resolutions

So what will 2016 be like? Of course, I will be contributing more. As a developer I find really challenging and exciting working on an open source software with so many competent contributors. There’s so much to learn!

And what about WordCamps? Well, I have already purchased my ticket for WordCamp Europe in Vienna, so let’s see if I break my 2015’s attendance record!

List the size of folders recursively in Linux

I needed a summary of how much space the single subfolders where taking on disk. You can use the du command, with the right flags

du -skh *

Here is an example output

giustino:~/tmp/VVV  (develop *)
⇒ du -skh *
220K    config
32K database
8,0K    log
36K provision
16K Vagrantfile
4,0K    wp-cli.yml
411M    www

Icon and Splash screen in Phonegap

I’ve been working with Phonegap lately.. This is a note to my future self about icons and splash screen

  1. The config.xml should be in the www folder
  2. You should add a icon.png and splash.png in the same folder as the config.xml


<icon src="res/icon/android/mdpi.png" gap:platform="android" gap:qualifier="mdpi" />
<icon src="res/icon/android/hdpi.png" gap:platform="android" gap:qualifier="hdpi" />
<icon src="res/icon/android/xhdpi.png" gap:platform="android" gap:qualifier="xhdpi" />
<icon src="icon.png" gap:role="default" />
<!-- Define app splash screen for each platform. -->
<gap:splash src="splash.png" />