Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" | |
"http://www.w3.org/TR/html4/strict.dtd"> | |
<html lang="en"> | |
<head> | |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | |
<title><img src="Matterful"></title> | |
<meta name="generator" content="TextMate http://macromates.com/"> | |
<meta name="author" content="Chase Reeves"> | |
<!-- Date: 2012-04-04 --> |
<?php | |
/* | |
Usage: | |
$frag = new CWS_Fragment_Cache( 'unique-key', 3600 ); // Second param is TTL | |
if ( !$frag->output() ) { // NOTE, testing for a return of false | |
functions_that_do_stuff_live(); | |
these_should_echo(); | |
// IMPORTANT | |
$frag->store(); | |
// YOU CANNOT FORGET THIS. If you do, the site will break. |
<?php | |
//=========================================================== SIDEBAR == Similar Posts | |
function similar_posts() { | |
echo "<li class=\"widget similar_posts\">"; | |
echo "<h3>Similar Posts</h3>"; | |
echo "<ul>"; | |
global $post; | |
//stores the original post data | |
$original_post = $post; |
user www-data; | |
worker_processes 4; # number of cores on machine | |
error_log /var/log/nginx/error.log; | |
events { | |
worker_connections 1024; | |
} | |
http { |
#!/usr/bin/env python | |
#install the follow first: | |
#sudo easy_install pip | |
#sudo pip install -U boto | |
#sudo pip install configparser |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
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
### Keybase proof | |
I hereby claim: | |
* I am williejackson on github. | |
* I am williejackson (https://keybase.io/williejackson) on keybase. | |
* I have a public key whose fingerprint is 38B3 317B A51C C073 490F BB92 AFDA 967F 9308 AFDA | |
To claim this, I am signing this object: |