Inguss Neilands IngussNeilands

Continuous Integration - Know your opportunities

Continuous Integration in a nutshell

Continuous Integration (CI) is an important practice every team should adopt in order to detect defects and errors early and solve integration problems easily. Roughly speaking we may say that CI is a practice that allows the growth of solid software by giving greater confidence to the developers and better products to the final customers.

The concept behind CI is fairly simple: the codebase is owned by several developers that continuously integrate their changes to a common version control system. For each integration the system runs a predefined set of tasks automatically; these tasks may vary from running all the tests to building all the components.

Jenkins, Protractor and Headless Chrome Browser Setup on Ubuntu 14.04

Update Ubuntu

sudo apt-get update
sudo apt-get upgrade

Install Java

Linux Backup Solutions

I've been looking for the best Linux backup system, and also reading lots of HN comments.

Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.

Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.

Amanda (comments by sammcj)

It has a lot of management overhead and that's a problem if you don't have time for a full time backup administrator.

	#!/bin/bash
	# collectd plugin to monitor passenger
	# has better memory-requirement than a ruby script
	# TODO: try writing it in c - if it makes a difference

	HOSTNAME="production-host-01"
	INTERVAL="${COLLECTD_INTERVAL:-10}"
	PLUGIN_NAME="passenger_status"

	while sleep "$INTERVAL"


	###GOOGLE Console DEV
	Original JavaScript autorized
	http://grafana.mydomain.com.br

	URIs redirect autorized
	http://grafana.mydomain.com.br:3000/login/google

	### NGINX PROXY
	server {

	# /etc/systemd/system/docker.service.d/docker-nftables.conf
	# disable iptables in docker, allowing nftables to do work
	[Service]
	ExecStart=
	ExecStart=/usr/bin/docker daemon -H fd:// --iptables=false

	#
	# This config file is a combination of ideas from:
	# http://www.37signals.com/svn/posts/1073-nuts-bolts-haproxy
	# http://www.igvita.com/2008/05/13/load-balancing-qos-with-haproxy/
	# http://wiki.railsmachine.com/HAProxy
	# http://elwoodicious.com/2008/07/15/nginx-haproxy-thin-fastcgi-php5-load-balanced-rails-with-php-support/
	# http://upstream-berlin.com/2008/01/09/using-haproxy-with-multiple-backends-aka-content-switching/
	# http://wiki.railsmachine.com/HAProxy
	# http://gist.github.com/raw/25482/d39fb332edf977602c183194a1cf5e9a0b5264f9
	#

	frontend https-in
	mode tcp
	bind *:443 ssl crt /etc/ssl/dummy.pem alpn h2,http/1.1
	use_backend nodes-http2 if { ssl_fc_alpn -i h2 }
	default_backend nodes-http

	backend nodes-http
	server node1 web.server:80 check

	backend nodes-http2

	digraph architecture {
	rankdir=LR;

	// Storage - #303F9F (dark blue)
	node[fillcolor="#303F9F" style="filled" fontcolor="white"];
	database[label="DB"]; cache[label="Redis"];

	// Client-side Apps - #FFEB3B (yellow)
	node[fillcolor="#FFEB3B" style="filled" fontcolor="black"];
	front_end[label="Front-end App"]; extension[label="Browser Extension"];

	#host running out of memory!
	ALERT HighMem
	IF 100 -(node_memory_MemFree + node_memory_Buffers + node_memory_Cached) / node_memory_MemTotal* 100 > 80
	FOR 1m
	WITH {
	severity="page"
	}
	SUMMARY "Instance {{$labels.host}} has high memory consumption"
	DESCRIPTION "{{$labels.host}} of job {{$labels.job}} has less than 40% of memory available for more than 1 minutes."