Skip to content

Instantly share code, notes, and snippets.

View Finkes's full-sized avatar

Dominik Finkbeiner Finkes

View GitHub Profile
This file has been truncated, but you can view the full file.
ISO-10303-21;
HEADER;
FILE_DESCRIPTION (( 'STEP AP214' ),
'1' );
FILE_NAME ('fan-007-M1.STEP',
'2024-04-15T13:19:59',
( '' ),
( '' ),
'SwSTEP 2.0',
'SolidWorks 2023',
@Finkes
Finkes / header_debug.kubernetes.yaml
Created November 22, 2021 12:08
Debug headers inside a kubernetes cluster behind a nginx ingress
apiVersion: apps/v1
kind: Deployment
metadata:
name: debug-headers
namespace: your-namespace
labels:
app: debug-headers
spec:
selector:
matchLabels:
We can make this file beautiful and searchable if this error is corrected: Any value after quoted field isn't allowed in line 2.
name,ring,quadrant,isNew,description
Composer,adopt,tools,TRUE,"Although the idea of dependency management ..."
Canary builds,trial,techniques,FALSE,"Many projects have external code dependencies ..."
Apache Kylin,assess,platforms,TRUE,"Apache Kylin is an open source analytics solution ..."
JSF,hold,languages & frameworks,FALSE,"We continue to see teams run into trouble using JSF ..."
@Finkes
Finkes / ProceduralTerrain.cs
Created October 11, 2019 21:03
Procedural Terrain for Unity
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class ProceduralTerrain : MonoBehaviour
{
Vector3[] vertices;
int[] triangles;
Mesh mesh;
@Finkes
Finkes / JsonRestClient
Created October 21, 2016 00:23
JSON REST Client for Unity 3D
using UnityEngine;
using System.Collections;
using UnityEngine.Networking;
public class JsonRestClient : MonoBehaviour {
private T fromJSON<T>(string json){
return JsonUtility.FromJson<T> (json);
}
import {Directive, Input, ElementRef} from '@angular/core';
@Directive({
selector: '[tooltip]',
host: {
'(mouseenter)': 'show($event)'
}
})
export class Tooltip {
constructor(element: ElementRef){
@Finkes
Finkes / Instructions.md
Created August 14, 2016 21:26 — forked from shreyaskarnik/Instructions.md
Route Docker Logs to ELK Stack
  • With Docker 1.8.0 shipped new log-driver for GELF via UDP, this means that the logs from Docker Container(s) can be shipped directly to the ELK stack for further analysis.
  • This tutorial will illustrate how to use the GELF log-driver with Docker engine.
  • Step 1: Setup ELK Stack:
    • docker run -d --name es elasticsearch
    • docker run -d --name logstash --link es:elasticsearch logstash -v /tmp/logstash.conf:/config-dir/logstash.conf logstash logstash -f /config-dir/logstash.conf
    • Note the config for Logstash can be found at this link
    • docker run --link es:elasticsearch -d kibana
  • Once the ELK stack is up now let's fire up our nginx container which ships its logs to ELK stack.
  • LOGSTASH_ADDRESS=$(docker inspect --format '{{ .NetworkSettings.IPAddress }}' logstash)
  • `docker run -d --net=host --log-driver=gelf --log-opt gelf-address=u