input { | |
lumberjack { | |
# The port to listen on | |
port => 5043 | |
# The paths to your ssl cert and key | |
ssl_certificate => "/etc/pki/tls/certs/logstash-forwarder/logstash-forwarder.crt" | |
ssl_key => "/etc/pki/tls/private/logstash-forwarder/logstash-forwarder.key" | |
# default type, but this will already be set by logstash-forwarder anyways |
Tested under webpack-dev-server 1.7.0.
- Clone this gist
npm install
npm start
- Visit http://localhost:8080 (or http://192.168.x.x:8080) on multiple devices
- Edit entry.js and hit save
While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
function wp_api_encode_acf($data,$post,$context){ | |
$data['meta'] = array_merge($data['meta'],get_fields($post['ID'])); | |
return $data; | |
} | |
if( function_exists('get_fields') ){ | |
add_filter('json_prepare_post', 'wp_api_encode_acf', 10, 3); | |
} |
angular.module('globalmodule') | |
.config(['$provide', '$httpProvider', function($provide, $httpProvider){ | |
$provide.factory('GlobalAjaxInterceptor', ['$q', '$rootScope', function($q, $rootScope){ | |
var currentRequests={http: {}, ajax: {}}; | |
function addHttpRequest(conf){ | |
currentRequests.http[conf.url] = conf.promiseObj; | |
} |
// Requires https://www.npmjs.org/package/s3-policy and https://www.npmjs.org/package/node-uuid | |
var config = require('env/' + process.env.NODE_ENV), | |
policy = require('s3-policy'), | |
uuid = require('node-uuid'); | |
// SETUP S3 | |
const AWS_ACCESS_KEY = config.s3.accessKey; | |
const AWS_SECRET_KEY = config.s3.secret; | |
const S3_BUCKET = config.s3.bucket; |
# There was a day where I have too many color schemes in iTerm2 and I want to remove them all. | |
# iTerm2 doesn't have "bulk remove" and it was literally painful to delete them one-by-one. | |
# iTerm2 save it's preference in ~/Library/Preferences/com.googlecode.iterm2.plist in a binary format | |
# What you need to do is basically copy that somewhere, convert to xml and remove color schemes in the xml files. | |
$ cd /tmp/ | |
$ cp ~/Library/Preferences/com.googlecode.iterm2.plist . | |
$ plutil -convert xml1 com.googlecode.iterm2.plist | |
$ vi com.googlecode.iterm2.plist |
# The next line updates PATH for the Google Cloud SDK. | |
source /Users/dwchiang/google-cloud-sdk/path.zsh.inc | |
# The next line enables zsh completion for gcloud. | |
source /Users/dwchiang/google-cloud-sdk/completion.zsh.inc |