Potherca

OpenID Connect Core

Abstract Flow

+--------+                                   +--------+
|        |                                   |        |
|        |---------(1) AuthN Request-------->|        |
|        |                                   |        |
|        |  +--------+                       |        |

rayjohnson

I use the QNAP nas server to host docker containers.  We can configure
this mac to run docker-machine and point to the qnap server to deploy or 
otherwise mess with docker.

This is how we set that up:
docker-machine create --driver=none --url tcp://<your qnap box>:2376 qnap


Next we need to install the certs.  Download them from within the QNAP

artemave

# config/initializers/carrierwave.rb

require 'mini_magick'

module CarrierWave
  module MiniMagick
    # round _square_ image
    def round
      manipulate! do |img|
        img.format 'png'

gabrielemariotti

        Toolbar toolbar = (Toolbar)findViewById(R.id.toolbar);
        
        //Title and subtitle
        toolbar.setTitle("MY toolbar");
        toolbar.setSubtitle("Subtitle");

        //Menu
        toolbar.inflateMenu(R.menu.toolbar_menu);

        toolbar.setOnMenuItemClickListener(new Toolbar.OnMenuItemClickListener() {

gcarrion-gfrmedia

# Install Git needed for Git based gems
packages:
  yum:
    git: []
    

DanHerbert

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

gpessia

/**
 * Helvetica Neue Normal (No Stretch)
 */

/* Helvetica Neue Black Font Stack */
.{font-family: "HelveticaNeueBlack", "HelveticaNeue-Black", "Helvetica Neue Black", "HelveticaNeue", "Helvetica Neue", 'TeXGyreHerosBold', "Arial Black", sans-serif; font-weight:800; font-stretch:normal;}

/* Helvetica Neue Heavy Font Stack */
.{font-family: "HelveticaNeueHeavy", "HelveticaNeue-Heavy", "Helvetica Neue Heavy", "HelveticaNeue", "Helvetica Neue", 'TeXGyreHerosBold', "Arial Black", sans-serif; font-weight:700; font-stretch:normal;}

chriswessels

#Meteor and Self-hosted Infrastructure

Meteor is an eye-opening JavaScript framework that runs on both the client and the server, giving developers a revolutionary take on software engineering. If you are not familiar with Meteor, I urge you to visit their website.

##An overview

In this brief gist, I am going to discuss the process of setting up a server (in my case, a VPS) to host Meteor applications.

My experience with Meteor has been brief, however it has not taken much demonstration for me to realise the significance of this stellar framework. Let's jump right in!

miry

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE template SYSTEM "../../../project-config.dtd">

<template>
  <name>Rails</name>
  <settings>
    <options>
      <option name="executionTimeoutMin" value="20" />
    </options>
    <parameters>

alertor

# force HTTP to HTTPS - /etc/nginx/conf.d/nonssl.conf
server {
    listen       80;
    server_name  jira.example.com;
    access_log  off;
    return 301 https://$server_name$request_uri;
}

# /etc/nginx/conf.d/jira.conf
server {