Ole Michaelis OleMchls

## gist:7195553
node web-1 {
     $role = 'web-app-a'
	$has_apache = true;

	include php5
}

node web-2 {
       $role = 'web-app-b'
       $has_fcgi=true

## gist:7290586
Title:
Service Orientated Architecture to scale to infinity and beyond
or
Service Orientated Architecture for robust and scalable systems

Proposal:
Software Architecture is hard. And when your business grow, its getting even harder because scaling doesn’t come out the box and it’s not only the software which grows it’s also the team. So you have to find a way how to scale your software in a way that it stays easy maintainable for growing teams and scalable. I’d like to talk about Service Orientated Architecture in general and also share some experience and give some examples where SOA would save your ass and maybe places where SOA isn’t the best idea to implement.

## abstract.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                OleMchls
                / abstract.md
            
            
              Created
              November 16, 2013 13:51
            
          
    #Chat Robots Next Level Tooling
Developers are lazy! So we are really great in create tooling for our daily tasks. But these tooling has its weaknesses. We are creating a tons of scripts on our local maschine, sometimes we share them via git or other vcs systems. But all over all this tooling sucks when it comes to collaboration. But there is a way to escape this, Chat Robots.
We developers also love hanging out in chat rooms like campfire or jabber. Why not combine this tooling and the chat rooms via chat robots. Our tooling would be available to everyone without installing wired shell scripts and its super documented, no more questions like: “Do you have the deploy lock?” or “Did you already migrate the database?” - it’s all documented in the chat transcripts.
I’d like to introduce hubot, a easy customization chat robot build by the fine folks at github. Also show how you can automate your tooling and scripts to make them available to everyone in your company!

  
## problem.md

      
              1 file
            
          
              0 forks
            
          
              1 comment
            
          
              0 stars
            
          
                OleMchls
                / problem.md
            
            
              Created
              November 29, 2013 11:40
            
          
    I've a upload page, where I want to upload a file to S3 directly and want to enter some meta data. The S3 path is determined by the entered metadata, and all of this, meta data and S3 url should be stored on a backend.
I want to have a "framework" which pushes every change to the backend, I don't want to have a save btn and I want to display a warning when the user tryies to leave the page when upload isn't finished yet. If he leaves anyway I want to destroy all data in backend.
So I guess I need some sort of framework to contain and manage the application state. With a good backend (rails) api.

  
## index.php
<?php header('Surrogate-Control: "ESI/1.0"'); ?>
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <title>My super simple ESI example</title>
  </head>
  <body>
    <p>Hello world! This is my super simple ESI example.</p>
    <aside><esi:include src="my-other-service.example.com/sidebar.html" /></aside>

## index.html
<html>
<head>
  <script src="http://code.jquery.com/jquery-1.11.0.min.js"></script>
  <script src="http://mozilla.github.io/pdf.js/build/pdf.js"></script>
  <script src="http://vivin.net/pub/pdfjs/textlayerbuilder.js"></script>
</head>
<body>
    <div id="pdfContainer" class = "pdf-content">
    </div>
    <script>

## application.rb
config.assets.paths << Rails.root.join(Gem.loaded_specs['rails-assets-components-font-awesome'].full_gem_path, "vendor", "assets", "fonts", "components-font-awesome", "fonts")

## demo.rb
Librato::Metrics::Collector.new(50) do |collector|
  collector.measure = Users.count
end

## gist:4528e1fd031ea50fe30a
2014-06-20T22:47:47.159839+00:00 app[worker.1]:
2014-06-20T22:47:47.159847+00:00 app[worker.1]:    **** This file had errors that were repaired or ignored.
2014-06-20T22:47:47.159966+00:00 app[worker.1]:    **** Please notify the author of the software that produced this
2014-06-20T22:47:47.159987+00:00 app[worker.1]:    **** file that it does not conform to Adobe's published PDF
2014-06-20T22:47:47.160005+00:00 app[worker.1]:    **** specification.
2014-06-20T22:47:47.160007+00:00 app[worker.1]:
2014-06-20T22:47:58.650510+00:00 app[worker.1]: GPL Ghostscript 8.71: Failed to interpret TT instructions for glyph index 107 of font MUFUZY+MerriweatherSans-Bold. Continue ignoring instructions of the font.

## music.json
[
  "W-SXBYTgXhg",
  "jofNR_WkoCE",
  "X0DeIqJm4vM",
  "2WNrx2jq184",
  "JuMlHdxiIZ8",
  "D9HvS_niU50",
  "37ZaSINRDGM",
  "MWUJvTyl-m4",
  "U_hrYz_2uAk",
	node web-1 {
	$role = 'web-app-a'
	$has_apache = true;

	include php5
	}

	node web-2 {
	$role = 'web-app-b'
	$has_fcgi=true
	Title:
	Service Orientated Architecture to scale to infinity and beyond
	or
	Service Orientated Architecture for robust and scalable systems

	Proposal:
	Software Architecture is hard. And when your business grow, its getting even harder because scaling doesn’t come out the box and it’s not only the software which grows it’s also the team. So you have to find a way how to scale your software in a way that it stays easy maintainable for growing teams and scalable. I’d like to talk about Service Orientated Architecture in general and also share some experience and give some examples where SOA would save your ass and maybe places where SOA isn’t the best idea to implement.
	<?php header('Surrogate-Control: "ESI/1.0"'); ?>
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>My super simple ESI example</title>
	</head>
	<body>
	<p>Hello world! This is my super simple ESI example.</p>
	<aside><esi:include src="my-other-service.example.com/sidebar.html" /></aside>
	<html>
	<head>
	<script src="http://code.jquery.com/jquery-1.11.0.min.js"></script>
	<script src="http://mozilla.github.io/pdf.js/build/pdf.js"></script>
	<script src="http://vivin.net/pub/pdfjs/textlayerbuilder.js"></script>
	</head>
	<body>
	<div id="pdfContainer" class = "pdf-content">
	</div>
	<script>
	Librato::Metrics::Collector.new(50) do \|collector\|
	collector.measure = Users.count
	end
	2014-06-20T22:47:47.159839+00:00 app[worker.1]:
	2014-06-20T22:47:47.159847+00:00 app[worker.1]: **** This file had errors that were repaired or ignored.
	2014-06-20T22:47:47.159966+00:00 app[worker.1]: **** Please notify the author of the software that produced this
	2014-06-20T22:47:47.159987+00:00 app[worker.1]: **** file that it does not conform to Adobe's published PDF
	2014-06-20T22:47:47.160005+00:00 app[worker.1]: **** specification.
	2014-06-20T22:47:47.160007+00:00 app[worker.1]:
	2014-06-20T22:47:58.650510+00:00 app[worker.1]: GPL Ghostscript 8.71: Failed to interpret TT instructions for glyph index 107 of font MUFUZY+MerriweatherSans-Bold. Continue ignoring instructions of the font.
	[
	"W-SXBYTgXhg",
	"jofNR_WkoCE",
	"X0DeIqJm4vM",
	"2WNrx2jq184",
	"JuMlHdxiIZ8",
	"D9HvS_niU50",
	"37ZaSINRDGM",
	"MWUJvTyl-m4",
	"U_hrYz_2uAk",