DaniSancas

Neo4j Tutorial

Fundamentals

Store any kind of data using the following graph concepts:

• Node: Graph data records
• Relationship: Connect nodes (has direction and a type)
• Property: Stores data in key-value pair in nodes and relationships
• Label: Groups nodes and relationships (optional)

datakurre

# -*- coding: utf-8 -*-
import aioamqp


connection = None
protocol = None


async def disconnected(exception):
    global connection, protocol

cotsog

sudo: required
script:
  - sudo unlink /usr/bin/gcc && sudo ln -s /usr/bin/gcc-5 /usr/bin/gcc
  - gcc --version
addons:
  apt:
    sources:
    - ubuntu-toolchain-r-test
    packages:
    - gcc-5

hgfischer

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

• Go HTTP standalone (as the control group)
• Nginx proxy to Go HTTP
• Nginx fastcgi to Go TCP FastCGI
• Nginx fastcgi to Go Unix Socket FastCGI

ngrilly

package auth

import (
	"net/http"
	"net/url"
	"strings"
	"time"

	"lib/crypto"
	"lib/utils"

juliendsv

#!/bin/bash

sudo mkdir /db/tmpfs
sudo mount -osize=256m tmpfs /db/tmpfs -t tmpfs
sudo chmod 777 /db/tmpfs

# IMPORTANT edit your /etc/apparmor.d/usr.sbin.mysqld
# to match your new path
# so /var/lib/mysql -> /db/tmpfs/mysql/ (there must be 2 links)
# Then restart apparmor /etc/init.d/apparmor restart

karlwestin

  /*
   * Use this to turn on logging: (in your local extensions file)
   */
  Handlebars.logger.log = function(level) {
    if(level >= Handlebars.logger.level) {
      console.log.apply(console, [].concat(["Handlebars: "], _.toArray(arguments)));
    }
  };
  // DEBUG: 0, INFO: 1, WARN: 2, ERROR: 3, 

bradland

# This is a short collection of tools that are useful for managing your
# known_hosts file. In this case, I'm using the '-f' flag to specify the
# global known_hosts file because I'll be adding many deploy users on this
# system. Simply omit the -f flag to operate on ~/.ssh/known_hosts

# Add entry for host
ssh-keyscan -H github.com >> /etc/ssh/ssh_known_hosts

# Scan known hosts
ssh-keygen -f /etc/ssh/ssh_known_hosts -F github.com