ekristen

#!/bin/bash

# Author: Erik Kristensen
# Email: [email protected]
# License: MIT
# Nagios Usage: check_nrpe!check_docker_container!_container_id_
# Usage: ./check_docker_container.sh _container_id_
#
# Depending on your docker configuration, root might be required. If your nrpe user has rights
# to talk to the docker daemon, then root is not required. This is why root privileges are not

soarez

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

kevin-smets

Default

Powerlevel10k

esfand

Embedded Variables

The ngx_http_core_module module supports embedded variables with names matching the Apache Server variables. First of all, these are variables representing client request header fields, such as $http_user_agent, $http_cookie, and so on. Also there are other variables:

• $arg_name
  argument name in the request line

JesseObrien

<?php

class MyModel extends Eloquent {
  
  public function getSql() 
  {
    $builder = $this->getBuilder();	
    $sql = $builder->toSql();
    foreach($builder->getBindings() as $binding)
    {

Gazer

server {
  listen 80;

  server_name localhost;

  location @until {
    # Static "comming soon" directory with index.html and assets
    root /var/www/;
    index index.html;
  }

cschlyter

var mention_id = 620996;

db.mentionStats.aggregate([
    { $match: {'mention_id': mention_id}},
    { $group: {'_id': {
                    'year': { '$year': "$verification_date" },
                    'month': { '$month': "$verification_date" },
                    'day': { '$dayOfMonth': "$verification_date" }
                },
                'retweets': { $last: "$retweets" }}},

hzbd

global
    pidfile /var/run/haproxy.pid
    log 127.0.0.1 local0 info
    ulimit-n        65536

defaults
    mode http

    clitimeout          600000   # maximum inactivity time on the client side
    srvtimeout          600000   # maximum inactivity time on the server side

chakrit

TMUX - Single window group, multiple session.

So I have been using tmux for a while and have grown to like it and have since added many many customizations to it. Now once you start getting the hang of it, you'll naturally want to do more with the tool.

Now tmux has a concept of window-group and session and if you are like me you'll want multiple session that connects to the same window group instead of a new window group every time. Basically I just need different views into the same set of windows that I have already created, I don't want to create a new set of windows every time I fire up my terminal.

This is the default case if you simply use the tmux command as your login shell, effectively creating a new group of windows every time you start tmux.

This is less than ideal because, if you are like me, you fire up one-off terminals all the time and you don't want all those one-off jobs to stay running in the background. Plus sometimes you need information fro

uris77

# This is a very crud example of using the Repository Pattern with SQLAlchemy. It allows me to completely ignore interactions with 
# the database. This is only pulled in whenever I require to persist or retrieve an object from the database. The domain/business 
# logic is entirely separated from persistence and I can have true unit tests for those.

# The tests for persistence are then limited to very specific cases of persistence and retrieving instances, and I can do those 
# independent of the business logic. They also tend to be less tests since I only need to test them once.