Web server in go

So what exactly is a container and how is it different from hypervisor-based virtualization? To put it simply, containers virtualize at the operating system level, whereas hypervisor-based solutions virtualize at the hardware level. While the effect is similar, the differences are important and significant, which is why I'll spend a little time exploring the differences and the resulting differences and trade-offs.

Welcome to the OpenGL Programming book. OpenGL is an API used for drawing 3D graphics. OpenGL is not a programming language; an OpenGL application is typically written in C or C++. What OpenGL does allow you to do is draw attractive, realistic 3D graphics with minimal effort. The API is typically used to interact with a GPU, to achieve hardware-accelerated rendering.

Gitchain is an application of the exciting ideas behind Bitcoin, Namecoin and DHT applied to Git hosting. Once you install it, it acts as a local proxy to the entire Gitchain P2P network.

php -S 127.0.0.1:8080

Mettre son projet en production, c’est la galère. Tellement que mille méthodes on vu le jour pour automatiser tout ça. Chef, salt, fabric, des script bash, virtualenv, git hooks, etc.

Après, il y a ceux qui utilisent des VM. Qui ont leur propres outils d’automatisation type Vagrant.

Et comme ça suffit pas, des services ce sont mis en place pour faciliter la mise en prod dans le cloud comme heroku, gondor…

Malgré ça, Max fait encore beaucoup de truc à la main parce que “ça marche jamais comme prévu”. Pas très scalable.

Dernièrement, grâce à notre cher Cortex, j’ai découvert un projet écrit en Go nommé Docker, qui propose encore une autre approche du problème.

How to use lib lua

for i in pidof python; do cat /proc/$i/cmdline | tr "\0" " " | sed "s/$/ $i\n/"; done

Useful when you have permission problem on which permission policykit handles. (network disk mounting power management ...)

If your problem seems related to debconf database corruption, be it of
above kind or not, the suggested fix is, quoting Joey Hess message in
#198297 bug page

By purging and reinstalling the package, you only fixed the entries for
that package. I suggest you run /usr/share/debconf/fix_db.pl as root,
which will delete all the orphaned questions. You may end up having to
repeat your answers to some debconf questions during future upgrades,
but that's a small price to pay for a consistent debconf database.

After running /usr/share/debconf/fix_db.pl as root, please look which
templates were affected,

$ diff -u /var/cache/debconf/config.dat{-old,} | grep ^[+-]Name
$ diff -u /var/cache/debconf/templates.dat{-old,} | grep ^[+-]Name

Your debconf database should be now in a consistent state and packages
configuration should succeed.

Most linux distributions use some type of mechanism to gracefully stop daemons and unmount storage volumes during a reboot or shutdown. It’s most commonly done via scripts that will wait for each daemon to shut down gracefully before proceeding to the next daemon.

As we know, sometimes servers misbehave due to things put them through, and you can quickly end up in a situation where things are going badly