Adam Tuttle atuttle

[DISCORD SERVER] Code of Conduct

Welcome!

[BRIEF DESCRIPTION OF THE DISCORD SERVER AND ITS PURPOSE]

The current admins are:

[NAMES]

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo

io.js - what you need to know

io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
io.js will be totally compatible with node.js
the people who created io.js are node core contributors who have different ideas on how to run the project
it is not a zero-sum game. many core contributors will help maintain both node.js and io.js

CentOS 6.x Install Instructions

####Preface

These are my own instructions that I have decided to document as I have gone along. I have put them out there in case others may find them useful, but I make no guarantees on their accuracy, or even if any of it is a good idea! I am no linux/rabbitmq/redis/postgres/tomcat/etc expert, hence why I need these instructions. These are setups for what I needed at the time I wrote them, they may not be appropriate for you. If you have suggestions on how to improve any of this, or notice anything wrong, please let me know / fork the guide and make the changes.

When this guide was started Cent 6.3 was the latest version. I have since used the same instructions for 6.4 and 6.5 without issue. Just update any references to 6.3 to the latest version when you use this guide.

Be careful copying and pasting commands. Make sure before you do that none of the filenames or versions have changed since the guide was written. It is common for the

Open Conference Expectations

This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.

We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.

These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea

	<html>
	<head>
	<title>JS File Upload</title>
	<script src="//ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
	</head>
	<body>
	<input type="file" id="inpFile" value="" />
	<input type="button" id="btnUpload" value="upload" />

	<script>

	1. Monolithic applications and architectures can vary in their monolithness. This is an under-specified description.
	2. Microservice applications and architectures can vary in their microness. This is an under-specified description.
	3. Microservices and monolithic architectures have both benefits and disadvantages.
	4. Organizations will exploit those benefits while working around any weaknesses.
	5. Success of the business is a large influence on the exploitation of benefits and implementation and costs of workarounds.
	6. All benefits and work arounds are context-sensitive. Meaning that they are both technically and socially constructed by the organization that navigates them.
	7. Path dependency is a thing. History matters and manifests in these architectural decisions and evolution in an organization.
	8. Patterns exist to inform practice, not dictate it. Zealous adherence to an architectural pattern brings peril when it is to the exclusion of cultural context in actual practice.
	9. Architectural patterns w

	#!/usr/bin/env python
	# fix an Android APK built by PhoneGap Build to correct the problem of
	# xhdpi images not being correctly added (https://github.com/phonegap/build/issues/9)
	#
	# REQUIRES apktool and jarsigner to already be installed and on the PATH.
	#
	# usage: fix_android_apk.py www/config.xml InputFile.apk OutputFile.apk
	#

	import os,sys,shutil,tempfile,xml.dom.minidom

	<!--- set up app --->
	<cfapplication name="ratelimit"/>
	<cfif not StructKeyExists(application,"limiter") or StructKeyExists(url,"reset")>
	<cfset application.limiter = CreateObject("component","TimeBasedRateLimiter")/>
	</cfif>

	<!--- check our limiter --->
	<cfif application.limiter.requestsRemaining() gt 0>
	<cfset application.limiter.push() />
	<p>Request was successful.</p>