torbjornvatn

kibana_host: logstash.openstack.org
alerts:
  messagealert2:
    field: message
    query: eyJzZWFyY2giOiIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6OTAwLCJncmFwaG1vZGUiOiJjb3VudCJ9
    limit: 10

owaism

Deploying Cloud Foundry to AWS - VPC

I worte this up because the instructions present in Cloud Foundry Docs led to loads of issues which required a lot of research. The Instruction provided here will simplify any subsequent deploys.

So till I find time to automate the deployment here are the instructions.

##Recommendations

1. In the below instructions for AWS keys, use a user who belongs to administrators group. You will understand it as you go forward with the instructions.
2. Start with a clean AWS account with nothing installed on it.

vStone

#!/bin/sh
#
# Installation:
#   To use this script, place it in the commands directory of your
#   gitolite installation. (Hint: ~/gitolite/src/commands/)
#   You will also have to add the command to the allowed commands in
#   your .gitolite.rc configuration file.
#
# Permissions:
#   The script requires the same permissions as the desc command.

doug2k1

/*
 The purpose of this script is to daily check Packt's Free Book offer 
 and notify via e-mail with the title of the book and link to download page
 -> https://www.packtpub.com/packt/offers/free-learning
 
 Author: Douglas Matoso - www.dmatoso.com
 
 Instructions:
 1) Create a new Google Script at http://script.google.com
 2) Paste the code below, putting your email in the "email" var.

der3k

@Grab('org.asciidoctor:asciidoctor-java-integration')
import org.asciidoctor.Asciidoctor
import org.asciidoctor.Attributes
import org.asciidoctor.OptionsBuilder
import org.asciidoctor.SafeMode

import static org.asciidoctor.Asciidoctor.Factory.create

//println 'Starting...'

jed

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                    Version 2, December 2004

 Copyright (C) 2011 Jed Schmidt <http://jed.is>

 Everyone is permitted to copy and distribute verbatim or modified
 copies of this license document, and changing it is allowed as long
 as the name is changed.

            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE

AutomationD

<filetype binary="false" description="Logstash Config" name="Logstash Config">
  <highlighting>
    <options>
      <option name="LINE_COMMENT" value="#" />
      <option name="COMMENT_START" value="" />
      <option name="COMMENT_END" value="" />
      <option name="HEX_PREFIX" value="" />
      <option name="NUM_POSTFIXES" value="" />
      <option name="HAS_BRACES" value="true" />
      <option name="HAS_BRACKETS" value="true" />

evansd

# Apt-install various things necessary for Ruby, guest additions,
# etc., and remove optional things to trim down the machine.
apt-get -y update
apt-get -y remove apparmor
apt-get -y install linux-headers-$(uname -r) build-essential
apt-get -y install zlib1g zlib1g-dev libxml2 libxml2-dev libxslt-dev libssl-dev openssl libreadline5-dev
apt-get clean

# Remove this file to avoid dhclient issues with networking
rm -f /etc/udev/rules.d/70-persistent-net.rules

pgchamberlin

Deploying Keycloak to AWS

The objective of this guide is to deploy Keycloak to AWS in a minimally complex way for testing and discovery purposes. This means using the standalone build of Keycloak backed with Hibernate H2. The result is not a production ready system. It won't scale, it won't survive significant load, it can't be clustered.

Mostly this Gist is a distillation of the Keycloak Server Installation guide for a specific use case: to spin up a quick and dirty Keycloak instance for testing and experimenting.

Steps

• Spin up and configure a Ubuntu AMI
• Install and configure Keycloak with an SSL cert

gerardorochin

input {

  file {
    type         => "php-error"
    path         => "/var/www/error_log"
    sincedb_path => "/opt/logstash/sincedb-access"
  }

}