infoslack

Keybase proof

I hereby claim:

• I am infoslack on github.
• I am infoslack (https://keybase.io/infoslack) on keybase.
• I have a public key whose fingerprint is 0A8E 272F E908 7839 39B9 01AC 37D6 BB52 CE7B ED4D

To claim this, I am signing this object:

infoslack

Namespaces & Cgroups

• Introduction to Linux namespaces - Part 1: UTS
• Introduction to Linux namespaces - Part 2: IPC
• Introduction to Linux namespaces - Part 3: PID
• Introduction to Linux namespaces - Part 4: NS (FS)
• Introduction to Linux namespaces – Part 5: NET
• Bê-á-bá dos cgroups, parte 1: escalonador e prioridades
• [Bê-á-bá dos cgroups, parte 2: montagem e "pinning" de CPU](https://www.ibm.com/developerworks/community/blo

infoslack

#include <err.h>
#include <netdb.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/stat.h>
#include <sys/socket.h>
#include <sys/types.h>

int main(int argc, char *argv[])
{

infoslack

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

infoslack

Criar super usuário:

$ sudo -u postgres createuser --superuser $USER

Adicionar extensões:

$ sudo -u postgres psql template1 -c 'create extension if not exists "hstore"'

infoslack

1. Introdução

• O que é Docker ?
• O que diferencia um container de uma máquina virtual ?
• O que são Namespaces ?
• Para que serve o Cgroups ?
• O que é Union file systems ?

2. Explorando o Docker

• Instalação
• Hello, Docker!

infoslack

FROM ruby:2.2.1

RUN apt-get update -qq && apt-get install -y \
	build-essential \
	nodejs \
	postgresql-client

ENV APP_HOME /app
RUN mkdir $APP_HOME
WORKDIR $APP_HOME

infoslack

# Run container
#
# docker run -v /tmp/.X11-unix:/tmp/.X11-unix \
#     -v $(pwd)/.telegram:/root/Downloads/Telegram \
#     -e DISPLAY=unix$DISPLAY \
#     infoslack/telegram
#
FROM ubuntu:14.04
MAINTAINER Daniel Romero <infoslack@gmail.com>

infoslack

#!/usr/bin/env bash

# check_freak.sh
# (c) 2015 Martin Seener

# Simple script which checks SSL/TLS services for the FREAK vulnerability (CVE 2015-0204)
# It will output if the checked host is vulnerable and returns the right exit code
# so it can also be used as a nagios check!

PROGNAME=$(basename $0)

infoslack

description "project api server config"

start on started project_name
stop on stopped project_name

pre-start script
  mkdir -p /var/log/puma
  chown www-data. /var/log/puma

  mkdir -p /var/run/puma