| # Plain Ol' Node | |
| node --max-old-space-size=1024 app.js # increase to 1gb | |
| node --max-old-space-size=2048 app.js # increase to 2gb | |
| node --max-old-space-size=3072 app.js # increase to 3gb | |
| node --max-old-space-size=4096 app.js # increase to 4gb | |
| node --max-old-space-size=5120 app.js # increase to 5gb | |
| node --max-old-space-size=6144 app.js # increase to 6gb | |
| # For pm2 | |
| pm2 start app.js --node-args="--max-old-space-size=1024" # increase to 1gb |
| The MIT License (MIT) | |
| Copyright (c) 2015 Justin Perry | |
| Permission is hereby granted, free of charge, to any person obtaining a copy of | |
| this software and associated documentation files (the "Software"), to deal in | |
| the Software without restriction, including without limitation the rights to | |
| use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of | |
| the Software, and to permit persons to whom the Software is furnished to do so, | |
| subject to the following conditions: |
A quick overview of the node.js streams interface with basic examples.
This is based on @brycebaril's presentation, Node.js Streams2 Demystified
Streams are a first-class construct in Node.js for handling data.
Think of them as as lazy evaluation applied to data.
A quick overview of the node.js streams interface with basic examples.
This is based on @brycebaril's presentation, Node.js Streams2 Demystified
Streams are a first-class construct in Node.js for handling data.
Think of them as as lazy evaluation applied to data.
| /** | |
| * Created by Paul on 10/7/2016. | |
| * GunDB v0.3 | |
| * inspired by https://github.com/pgte/pouch-redux-middleware | |
| * TODO: issue: stores duplicates in an object path.docs for removing redundant operations | |
| * - can be implemented with redux history, but same lot of data | |
| * - checking with gun, don't know how, yet | |
| * - another method is eventually to store timestamps (updated_at) in redux and only that in path.docs | |
| * TODO: issue: not quite async as it should be in certain areas | |
| */ |
| package com.opentok.media.avc; | |
| import java.io.IOException; | |
| import java.nio.ByteBuffer; | |
| import android.media.MediaCodec; | |
| import android.media.MediaCodecInfo; | |
| import android.media.MediaFormat; | |
| public class AvcEncoder { |
I start with a list and plan to create a comparison table.
http://www.w3.org/TR/WebCryptoAPI/
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
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:
var Article = require('../../../models/article');Those suck for maintenance and they're ugly.
| # this script is used to partition and mount a 'local' disk on AWS EC2 after provisioning | |
| # | |
| TARGETDISK='docker' | |
| RAWDISK=`(lsblk -P | grep ${TARGETDISK} | awk '{ print $1}' | uniq | awk -F= '{print $2}' | sed 's/\"//')` | |
| DISK="/dev/mapper/$RAWDISK" | |
| MOUNTDIR='/scratch' | |
| SWAPFILE="$MOUNTDIR/swapfile02" | |
| NOTMOUNTED=`(mount | grep $DISK | wc -l)` | |
| DISKSIZE=`lsblk -b --output SIZE -n -d $DISK` | |
| SWAPSIZE=`r=$((($DISKSIZE)/2000000000)) ; printf %d.%d ${r%??} ${r#${r%??}} | awk '{print int($1+0.5)}'` |
| import { Component } from "React"; | |
| export var Enhance = ComposedComponent => class extends Component { | |
| constructor() { | |
| this.state = { data: null }; | |
| } | |
| componentDidMount() { | |
| this.setState({ data: 'Hello' }); | |
| } | |
| render() { |