Skip to content

Instantly share code, notes, and snippets.

Kyle Nathan kylenathan

  • Lion Enterprises Ltd
  • Windsor, UK
Block or report user

Report or block kylenathan

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
cs3b /
Created Aug 14, 2017
Circle CI Config for Ember.js project with Yarn, and Latest Firefox
version: 2
working_directory: ~/selleo-mail-log
- image: circleci/node:latest-browsers
- checkout
- restore_cache:
key: dependency-cache-{{ checksum "package.json" }}
code0100fun / app_controllers_sign-in.js
Created Jun 8, 2015
Ember Simple AUth + Ember CLI Mirage
View app_controllers_sign-in.js
// app/controllers/sign-in.js
import Ember from 'ember';
export default Ember.Controller.extend({
actions: {
this.set('errors', null);
var params = { identification: this.get('email'), password: this.get('password') };
// Redirects to index route on success (configurable in config/environment.js)
this.get('session').authenticate('simple-auth-authenticator:oauth2-password-grant', params);
jed /
Last active Nov 26, 2019
How to set up stress-free SSL on an OS X development machine

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

  • Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

  • Use production SSL certificates locally. This is annoying

caseyohara / reserved_usernames.rb
Created Dec 9, 2011
A list of reserved usernames to avoid vanity URL collision with resource paths
View reserved_usernames.rb
# A list of possible usernames to reserve to avoid
# vanity URL collision with resource paths
# It is a merged list of the recommendations from this Quora discussion:
# Country TLDs found here:
# Languages found here:
You can’t perform that action at this time.