Skip to content

Instantly share code, notes, and snippets.

View jrah's full-sized avatar
🇬🇧
Working from home

James Home jrah

🇬🇧
Working from home
View GitHub Profile
@gilbitron
gilbitron / InvoicePaid.php
Created November 14, 2016 12:31
Convert the Laravel Spark invoice email to a notification email
<?php // app/Notifications/InvoicePaid.php
namespace App\Notifications;
use Illuminate\Bus\Queueable;
use Illuminate\Notifications\Notification;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Notifications\Messages\MailMessage;
use Laravel\Cashier\Invoice;
@astannard
astannard / lightning talk proposal.md
Last active June 13, 2016 11:59
React Conference lightning talk proposal

With all the plugins, boilerplate projects, SAAS and PAAS offerings plus great community support, what can be created in a weekend?

I will take you through the ups downs and highlights of using react at a Startup Weekend event, showing what can be achieved and how.

This will be a story of a wild weekend full of tips, framework and plugin summaries plus pictures from the weekend as the startup team attempt to validate an idea.

The talk will be a great insight into how react can help you rapidly prototype a business idea, with what went well and what went badly.

https://reactiveconf.com/

@jed
jed / how-to-set-up-stress-free-ssl-on-os-x.md
Last active February 27, 2025 16:31
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

@hallettj
hallettj / global-variables-are-bad.js
Created February 14, 2009 21:15
How and why to avoid global variables in JavaScript
// It is important to declare your variables.
(function() {
var foo = 'Hello, world!';
print(foo); //=> Hello, world!
})();
// Because if you don't, the become global variables.
(function() {