deanmlittle

A far from exhaustive list of reasons why mAPI is shit

1. While it's an acceptable bandaid for now, we probably shouldn't just wrap JSON-RPC. It's really slow, and there's no reason to run an HTTP server that accesses another HTTP server. It's pretty silly tbh.
2. Nobody likes C#. Like, nobody.
3. You shouldn't have to go and install an entire postgres database in parallel to a mining node (both of which just love to compete with eachother to consume maximum resources) just to offer people different fee rates. If you had to do something like this, SQLite would be a much more lightweight alternative, however in almost all cases, miners will probably want to just run their own mining consoles (like any other kind of API service provider would) where they manage all this stuff themselves, so in reality, a simple JWT with an exp field, a fee field and a signing secret without any kind of user management whatsoever is probably already sufficient. If you have strong opinions to the contrary about thi

bradycoye

import aws from 'aws-sdk'
import path from 'path'
import fs from 'fs'
aws.config.loadFromPath(path.resolve('credentials', 'aws_config.json'));
const ses = new aws.SES({apiVersion: '2010-12-01'});
const resetEmail = fs.readFileSync(path.resolve('emails', 'reset-password.html'), 'utf8');
const verifyEmail = fs.readFileSync(path.resolve('emails', 'verify-email.html'), 'utf8');
import {Constants} from 'parse-server'
import Promise from 'bluebird'

hassy

Deploying Parse Server on AWS

Note: this is a work-in-progress and will be updated with more information over the next few days.

Intro

This guide will walk you through deploying your own instance of the open-source Parse Server. This would be a good starting point for testing your existing application to see if the functionality provided by the server is enough for your application, and to potentially plan your migration off the Parse Platform.

This guide will walk you through using Elastic Beanstalk (EB), which is an AWS service similar to Heroku. Why use EB rather than Heroku? Elastic Beanstalk does not lock you into Heroku-specific ways of doing things, is likely cheaper to run your backend on than Heroku, and it integrates with other services that AWS offer (and they offer almost everything one needs to run an application these days).

kArTeL

Videos

• Introduction to Functional Programming Johannes Weiß - http://kcy.me/1ngiv
• ReactiveCocoa at MobiDevDay Andrew Sardone - http://kcy.me/1nhl3
• The Future Of ReactiveCocoa Justin Spahr-Summers - http://kcy.me/1nhs7
• Enemy of the State Justin Spahr-Summers - http://kcy.me/1njzs
• WWDC 2014 Session 229 - Advanced iOS Application Architecture and Patterns Andy Matuschak - http://kcy.me/1pyva
• Functioning as a Functionalist Andy Matuschak - http://kcy.me/22o45
• Controlling Complexity in Swift Andy Matuschak - http://kcy.me/23sc9
• Functional and reactive programming with Swift Ash Furrow -

patriciogonzalezvivo

Install Homebrew

ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)"

Add PATH to ~/.bash_profile and ~/.zshrc

export PATH=/usr/local/bin:$PATH