whyvez

#!/bin/bash
#
# Script to setup a Elastic Beanstalk AMI with geospatial libraries and postGIS
#
# sh aws_ami_prep.sh > aws_ami_prep.log 2>&1 &

# Go to ec2-user home directory
cd /home/ec2-user

# yum libraries

bryanrsmith

export class HttpClient {
	constructor(defaults) {
		this.defaults = defaults;
		this.interceptors = [];
		this.activeRequestCount = 0;
		this.isRequesting = false;
	}

	addInterceptor(interceptor) {
		this.interceptors.push(interceptor);

frontenddeveloping

(function(global) {
    'use strict';

    var JSON_TYPE_NAME = 'type';
    
    function getQueryString(queryParams) {
                var params = Object.keys(queryParams).map(function(paramName) {
            return [paramName, encodeURIComponent(queryParams[paramName])].join('=');
        });
        return '?' + params.join('&');

jimrutherford

//
//  CrashlyticsDestination.swift
//
//  Created by Jim Rutherford on 2015-12-10.
//

import UIKit
import Crashlytics

public class CrashlyticsDestination: BaseDestination {

ashishkakkad8

//
//  AFWrapper.swift
//  AFSwiftDemo
//
//  Created by Ashish on 10/4/16.
//  Copyright © 2016 Ashish Kakkad. All rights reserved.
//

import UIKit
import Alamofire

levivm

class SignUpMixin(object):
    """
    Mixin for the common SignUp methods
    """
    permissions = []
    profile_serializer = None
    group_name = None

    def create_token(self, user):
        return Token.objects.create(user=user)

xta

andreaantonioni

iOS Cell Registration & Reusing with Swift Protocol Extensions and Generics

A common task when developing iOS apps is to register custom cell subclasses for both UITableView and UICollectionView. Well, that is if you don’t use Storyboards, of course.

Both UITableView and UICollectionView offer a similar API to register custom cell classes:

public func register(_ cellClass: AnyClass?, forCellReuseIdentifier identifier: String)
public func register(_ nib: UINib?, forCellReuseIdentifier identifier: String)

marcelog

version: 0.1

phases:
  install:
    commands:
      - printenv
      - npm install
  build:
    commands:
      - npm run build

ptgamr

Intro

If you ever need a mobile application, you probably have an API endpoint to talk to. And if you're doing it right, you should have different environment for your API, usually it'll be: dev, staging, production.

The problem: How do we do the testing for our app?

We dont' want to perform test againts the production API. We need a way to teach our app to talk to different API environment. But what is the switch?

The naive way: