vivekkr12

import org.bouncycastle.asn1.ASN1Encodable;
import org.bouncycastle.asn1.DERSequence;
import org.bouncycastle.asn1.x500.X500Name;
import org.bouncycastle.asn1.x509.BasicConstraints;
import org.bouncycastle.asn1.x509.Extension;
import org.bouncycastle.asn1.x509.GeneralName;
import org.bouncycastle.asn1.x509.KeyUsage;
import org.bouncycastle.cert.X509CertificateHolder;
import org.bouncycastle.cert.X509v3CertificateBuilder;
import org.bouncycastle.cert.jcajce.JcaX509CertificateConverter;

jinxidoru

import * as http from 'http'
import * as _ from 'lodash'


//! In the standard implementation of http server, calling close is not guaranteed to close the
//! server.  Any idle connections being kept alive by clients will stay open until their timeout
//! is reached.  This is problematic for gracefully shutting down a process with an http server.
//! This function will create an http server that tracks the open connections.  On close, idle
//! connections are closed and any newly idled connection is immediately closed as well.  When there
//! are no more connections on the server, the 'empty' event is raised.

aindong

window.PainDiagramModal = React.createClass({
    statics: {
        open: function(){
            this.$dialog = $('#diagramModal');

            if (!this.$dialog.length) {
                this.$dialog = $('<div id="diagramModal" class="reveal-modal" data-reveal role="dialog"></div>')
                    .appendTo('body');
            }

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

paf31

Introduction

At DICOM Grid, we recently made the decision to use Haskell for some of our newer projects, mostly small, independent web services. This isn't the first time I've had the opportunity to use Haskell at work - I had previously used Haskell to write tools to automate some processes like generation of documentation for TypeScript code - but this is the first time we will be deploying Haskell code into production.

Over the past few months, I have been working on two Haskell services:

• A reimplementation of an existing socket.io service, previously written for NodeJS using TypeScript.
• A new service, which would interact with third-party components using standard data formats from the medical industry.

I will write here mostly about the first project, since it is a self-contained project which provides a good example of the power of Haskell. Moreover, the proces

ekristen

#!/bin/bash

# Author: Erik Kristensen
# Email: erik@erikkristensen.com
# 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

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

trodrigues

If you want to clone an svn repository with git-svn but don't want it to push all the existing branches, here's what you should do.

* Clone with git-svn using the -T parameter to define your trunk path inside the svnrepo, at the same time instructing it to clone only the trunk:
  
  git svn clone -T trunk http://example.com/PROJECT

* If instead of cloning trunk you just want to clone a certain branch, do the same thing but change the path given to -T:

  git svn clone -T branches/somefeature http://example.com/PROJECT