dracoblue.net

If you want to debug or enter your docker container, you might think that you will easily run a sshd server and that's fine. But it's wrong and most of all: it's not necessary.

Like @jpetazzo explained in "Docker SSHD considered evil": containers run with only one executable as main process. So if you want to have a sshd next to your php-fpm, you will need monit or supervisor to launch them. That's already 3 services in total!

That's why: keep your docker image clean!

But how to enter the container? There is a little tool called "nsenter" (available with util-linux >= 2.24)

If you are working on a new API for one of your projects, you might consider a media type like HAL or Collection+JSON as an option for structuring your API responses.

First of all, check out api-craft mailinglist or hal-discuss mailinglist for really good ontopic discussions about api architectures and media types.

Common JSON media types do not support a method parameter on relations

In HAL relations are defined in links, like this (e.g. self and http://example.org/rels/appointment/cancel):

{
     "_links": {
       "self": { "href": "/appointment/123" },
       "http://example.org/rels/appointment/cancel": { "href": "/appointment/123" }
     },
     "patient_id": "jsmith"
   }

Even though the relations for a patient appointment are available, it's not clear which http method to use.

I finally released a new major version of jsb.

With 2.0 there are two breaking changes (you might still use 1.x series, if you rely on those.

1. The global JsBehaviourToolkit got removed #20.
2. A input[hidden] cannot be used as data source anymore #17.

That's it.

But jsb 2.0 comes with some cool additions.

While working with the facebook api (to fetch data about a facebook page), I noticed the following error:

{
  "error": {
    "message": "Unsupported get request.",
    "type": "GraphMethodException",
    "code": 100
  }
}

While I was working on puppet-rvm, I noticed that the shell providers of puppet do not run as login shell.

This means:

exec { "echo $PATH"
  provider => "shell"
}

will have an empty path, because the .bashrc and others have not been loaded.