php zmq in docker and checking whether the C compiler works... no

 I spent 2 hours of what it lasts of my life trying to understand what was the problem on installing php's zmq extension in a docker running alpine as base image. I would like to share my experience here.

 During morning I would like to write supporting class for integrating zmq into our system and use it from inside containers where services are  supposed to run.

First I just added to Dockerfile the pecl install command, and expected it works:


News from Verona ( ReactJS Day - October, 5th, 2018)

I wrote some kind of report about ReacJS day - Verona, October, 5th. But my pc blocked (TODO: buy a new pc, once I understand which), I did not saved the document. I taked a screenshot.

My experiment on React.context will focus on edit state of a page. Currently the page is made of various components and some are switchable to edit-mode and view-mode. I want to add constraint that only one element in a page is on edit mode, and also to add the behavior of switch-to-view-mode-on-ESC-key.

Docker in a Docker

Running a docker container from inside a docker container, I mean.

Of course one can define an image that instanciate a container as its default command, and this would lead to an infinite loop of forks ... let's see

The infinite containment

docker run -v /var/run/docker.sock:/var/run/docker.sock -name whocare alwaysfork

Ok, that is bad and I will not describe.

My beloved DevOps tool, gnu make

Oh, yes, there is a lot of tool around for Really DevOps(TM).

But I just want to automate the task to sync remote folders with my working tree, anything else is managed with git, and that's fine.

So I thought: rsync + fuse (file system user level mounting, I hate to launch filezilla or similae)

But I really does not need gulp, grunt or anything else, a Makefile is enough, no?

javascript Promise chaining: augmenting the unique argument

There are two things that, IMHO, make code cleaner when using Promises Idioma:

  1. use an unique object argument (and its attributes as you would use argument legacy)
  2. return resolve with the object given as argument augmented by attribute of the action executed by the function

i.e., say I want to ask db for data about a person, I define the method (function) that got an object {person: {personstruct}} and return the augmented object {person:{personstruct}, contactdata: {contactdatastruct}}