sidwarkd

{
    "eventName": "[EVENT TO LISTEN FOR]",
    "url": "https://api.twilio.com/2010-04-01/Accounts/[ACCOUNT SID]/Messages",
    "requestType": "POST",
    "auth": {
        "username": "[ACCOUNT SID]",
        "password": "[AUTH TOKEN]"
    },
    "form": {
        "From" : "[YOUR TWILIO NUMBER]", 

mohitbhoite

// This #include statement was automatically added by the Particle IDE.
#include "InternetButton/InternetButton.h"


InternetButton b = InternetButton();

uint32_t workTime = 0;
uint32_t restTime = 0;

// Time definitions in milliseconds

rauchg

Minimum Viable Async with Node 6

With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.

This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async + await.

The promise

nrobinson2000

UPDATE:

I have moved this script over from a gist to a repository.

I have also made it super easy to install this utility:

curl -fsSL https://git.io/vwRRf | bash

Additional functions have also been added, including OTA flashing and manual DFU control. Find out more in the repository, https://github.com/nrobinson2000/po-util

derwiki

Adding an audit log to your Rails app

If you have any sort of administrative interface on your web site, you can easily imagine an intruder gaining access and mucking about. How do you know the extent of the damage? Adding an audit log to your app is one quick solution. An audit log should record a few things:

• controller entry points with parameter values
• permanent information about the user, like user_id
• transient information about the user, like IP and user_agent

Using the Rails framework, this is as simple as adding a before_action to your admin controllers. Here’s a basic version that I’m using in production.

sentinelt

/*
 * Allows to set arbitrary speed for the serial device on Linux.
 * stty allows to set only predefined values: 9600, 19200, 38400, 57600, 115200, 230400, 460800.
 */
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <asm/termios.h>

int main(int argc, char* argv[]) {

hinok

//
//                         I created standalone package, look here
//
//                            https://github.com/hinok/spejson
//

// ----
// libsass (v3.0.2)
// ----

lapastillaroja

import android.content.Context;
import android.content.res.TypedArray;
import android.graphics.Canvas;
import android.graphics.Rect;
import android.graphics.drawable.Drawable;
import android.support.v7.widget.LinearLayoutManager;
import android.support.v7.widget.RecyclerView;
import android.util.AttributeSet;
import android.view.View;

weapp

error_page 500 /500.html;
location /500.html{
    return 500 '{"error": {"status_code": 500,"status": "Internal Server Error"}}';
}

error_page 502 /502.html;
location /502.html{
    return 502 '{"error": {"status_code": 502,"status": "Bad Gateway"}}';
}

eabait

• NVD3 (http://nvd3.org/)
  • Initial evaluation: seems the most mature. Apparently, has bad documentation, and is hard to use without going to its source code.
• dimple (http://dimplejs.org/)
  • Initial evaluation: its main goal is to offer a simple API to create charts
• C3.js (http://c3js.org/)
  • Initial evaluation: highly customizable charting API.
• xCharts (http://tenxer.github.io/xcharts/)
  • Initial evaluation: "designed to be dynamic, fluid, and open to integrations and customization" seems to have a rather complex API though
• Vega (http://trifacta.github.io/vega/)
• Initial evaluation: intends to generate data visualizations from a JSON document. Charts can be generated server-side. Has an online editor http://trifacta.github.io/vega/editor/