| // @mixin grid($columnCount:12, $unitRatio: 3, $width: 100%) { | |
| // @param $columnCount | |
| // Qty of columns. Defaults to 12. | |
| // @param $unitRatio | |
| // Column to gutter ratio. All grids are ususally build around grid units. Defaults to 3. | |
| // @param $width | |
| // Grid width. If specified in %, grid automatically becomes fluid. | |
| // @return | |
| // CSS markup for fluid or fixed grid. | |
| @mixin grid($columnCount:12, $unitRatio: 3, $width: 100%) { |
| javascript:var websiteurl = prompt("Enter Website URL to test page load times. IE- yourdomain.com");window.open('http://' + websiteurl + '.loads.in'); |
Collection of some of my fav terminal aliases that i use often & collected from the web. This file will be updated with more aliases as i find more. Feel free to comment and share your fav aliases you use :)
###Follow these simple steps to add the following aliases:###
Google Public DNS IPv4 Addresses
Google Public DNS IPv6 Addresses
| // Modifications via StackOverflow | |
| You are receiving the data in the right order, but then you are using the shuffle() function on the images array $a_images you created . | |
| if you remove the shuffle($a_images); from your code it'll be just fine. | |
| and replace $image[link], $image[url] and // // $image[caption] with $image['link'], $image['url'] and $image['caption'] | |
| sorry for bad english |
| #!/bin/sh | |
| :<<END_DOC | |
| blocklist updater - for transmission | |
| Written by raidzero for linux | |
| BLOCKLIST_HOME is the directory where transmission keeps its blocklists | |
| END_DOC | |
| BLOCKLIST_HOME=~/.config/transmission/blocklists |
| #!/usr/bin/env sh | |
| # Download lists, unpack and filter, write to gzipped file | |
| curl -s https://www.iblocklist.com/lists.php \ | |
| | grep -A 2 Bluetack \ | |
| | sed -n "s/.*value='\(http:.*\)'.*/\1/p" \ | |
| | xargs wget -O - \ | |
| | gunzip \ | |
| | egrep -v '^#' \ | |
| | gzip - > bt_blocklist.gz |
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