wangshijun

TODO:

- edit /opt/statsd/local.js
  - correct the graphite host to localhost
  - if desired, put 'debug: true' in there
- make the box accessible via the hostname 'graphite'
- update conf/storage-schemas.conf, see example for these retention rules:
    6 hours of 10 second data
    1 week of 1 minute data
    5 years of 10 minute data

wangshijun

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.

wangshijun

var fakeReferrer = "http://porzky.com"
var targetUrl = "http://keyworddomains.com"

var casper = require('casper').create();

casper.start(fakeReferrer, function() {
	this.echo(this.getCurrentUrl());
});

casper.then(function(){

wangshijun

.markdown-here-wrapper {
  font-size: 16px;
  line-height: 1.8em;
  letter-spacing: 0.1em;
}


pre, code {
  font-size: 14px;
  font-family: Roboto, 'Courier New', Consolas, Inconsolata, Courier, monospace;