hayeshaugen

# sudo su -
# apt-get install openjdk-6-jdk
# apt-get install ant1.8

Source control, in this case svn:

# apt-get install subversion

Install Jenkins

bverc

/*
 * Copyright (C) 2008 The Android Open Source Project
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

j4mie

How to run Sentry in a subdirectory with nginx

Scenario: you already have an app running at http://your.server.com/ and you want to run Sentry at http://your.server.com/sentry/

I spend a few hours banging my head against this, and finally got it to work. There may be a better way, but I couldn't find it.

Warning: hacky.

nginx.conf (in server stanza)

lmacken

#!/usr/bin/env python
# linkify.py - Turns URLs into links.
#
# Using on a file:
#
#   $ linkify.py <filename>
#   <a href="http://lewk.org">http://lewk.org</a>
#
# Using within a pipeline:
#

ibeex

A warning occurred (42 apples)
An error occurred

papoms

var page = require('webpage').create();

page.onConsoleMessage = function (msg) {
    console.log('From Page Console: '+msg);
};

page.onInitialized = function() {
	page.evaluate(function () {
		"use strict";
		//The Referrer we want to set

arriolac

import android.annotation.TargetApi;
import android.content.Context;
import android.graphics.Matrix;
import android.graphics.drawable.Drawable;
import android.os.Build;
import android.util.AttributeSet;
import android.widget.ImageView;

/**
 * Created by chris on 7/27/16.

lost-theory

from flask import Flask, Blueprint, request

## blueprint ##################################################################

bp = Blueprint('category_functionality', __name__)

@bp.route('/')
def index(category):
    return "this is the index page for %r" % category

jaredhirsch

ETags: a pretty sweet feature of HTTP 1.1

HTTP caching review

HTTP provides two ways for servers to control client-side caching of page components:

• freshness may be based on a date or a token whose meaning is app-specific
• whether or not the client needs to confirm the cached version is up-to-date with the server

This breaks down as follows:

• Cache locally and don't check before using.

emil2k

/*
 * Copyright (c) 2017 Emil Davtyan
 * 
 * Permission is hereby granted, free of charge, to any person obtaining
 * a copy of this software and associated documentation files (the
 * "Software"), to deal in the Software without restriction, including
 * without limitation the rights to use, copy, modify, merge, publish,
 * distribute, sublicense, and/or sell copies of the Software, and to
 * permit persons to whom the Software is furnished to do so, subject to
 * the following conditions: