harssh

#! /bin/sh

### BEGIN INIT INFO
# Provides:          nginx
# Required-Start:    $all
# Required-Stop:     $all
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts the nginx web server
# Description:       starts nginx using start-stop-daemon

harssh

# Make mouse useful in copy mode
setw -g mode-mouse on

# Allow mouse to select which pane to use
set -g mouse-select-pane on

# Allow mouse dragging to resize panes
set -g mouse-resize-pane on

# Allow mouse to select windows

harssh

##############################
#  _
# | |_ _ __ ___  _   ___  __
# | __| '_ ` _ \| | | \ \/ /
# | |_| | | | | | |_| |>  < 
#  \__|_| |_| |_|\__,_/_/\_\
#
#############################

############################################################################

harssh

There are many (old) clients available:

• https://github.com/activenetwork/gattica
• https://github.com/tpitale/legato
• https://github.com/vigetlabs/garb

All are abandoned and you should not use them. The Google Analytics API is at v3 and they are all using an earlier version.

Use https://github.com/google/google-api-ruby-client (Google supported).

harssh

There are many (old) clients available:

• https://github.com/tpitale/legato (active, supports API v3)
• https://github.com/activenetwork/gattica
• https://github.com/vigetlabs/garb

The Google Analytics API is at v3 (at time of writing).

This example uses Google's Ruby API client to access Analytics. Use https://github.com/google/google-api-ruby-client (Google supported).

harssh

Consuming Google Analytics data from a NodeJs application using a service account

I didn't have a great time trying to implement a simple feature involving Google Analytics in one of my projects (nodejs web application).

My humble requirement was to collect some data (events) I was pushing to Google Analytics in order to create a simple report for my users. Since it isn't a critical report, my idea was to get the data once a day and cache it.

So, as simple as it seems, it has been a tough trip for me and I want to share the whole process with the community. I hope anyone trying to achive something similar gets to this article and find it helpful.

These are the main steps I had to take:

harssh

/var/log/td-agent/td-agent.log {
        size 200M
        rotate 6
        missingok
        create 644 td-agent td-agent
        compress
        delaycompress
        notifempty
        sharedscripts
        postrotate

harssh

# appサーバ用の設定
<source>
  type tail
  path /var/log/nginx/access.log
  format apache
  tag nginx.access
  pos_file /var/log/td-agent/nginx.pos
</source>

<match nginx.access>

harssh

@hitsthings Your API is worth considering, without a doubt. My remarks:

• It introduces new entities/method, which is not a big deal, but should be avoided if possible.
• Does not support multiple parent schemas ("classes"). The latter of course can be easily fixed by using an array instead of a String value for _type(s).
• I like that you're able to chose the property that holds the type information.
• I think parent properties should be included by default, which is in line with programmers intuition.

I came up with an alternative approach that keeps the changes to the current API to a bare minimum and leverages the way models are created and cached.

Alternative approach

harssh

var mongoose = require('mongoose');
var Schema = mongoose.Schema;
 
//Database connection 
var uristring = 'mongodb://localhost/test';
var mongoOptions = { };
 
mongoose.connect(uristring, mongoOptions, function (err, res) {
    if (err) { 
        console.log('Error when connecting to: ' + uristring + '. ' + err);