moved to own repo: https://github.com/helb/videogif
/** | |
* http://applemusic.tumblr.com/ | |
*/ | |
/** Ultra Light */ | |
@font-face { | |
font-family: "San Francisco"; | |
font-weight: 100; | |
src: url("https://applesocial.s3.amazonaws.com/assets/styles/fonts/sanfrancisco/sanfranciscodisplay-ultralight-webfont.woff2"); | |
} |
###Let's install Vagrant###
- Install VirtualBox: https://www.virtualbox.org/
- Install Vagrant: http://vagrantup.com/
###Select a Vagrant Box from https://vagrantcloud.com###
#add it to your list of boxes
vagrant box add hashicorp/precise32
#create a new folder for your project & init vagrant
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
Creating a solid base for your .htaccess
file. Currently includes RewriteBase, Security (against indexes, files, etc.), and Expires Headers (caching, performance).
- The URL REWRITES would go at the top of the file.
- The SECURITY and the WEB PERFORMANCE can go towards the bottom... before and WordPress or WP Super Cache items.
- UPDATE 2013-08-21: Added code for forcing either non-www or www. on URLs. Also added the MultiViews option.
- UPDATE 2013-08-23: Added specific code for
wp-config.php
- UPDATE 2013-10-04: Increased favicon expire time.
- UPDATE 2014-02-05: Removed the Force URL rewrites since there's more than one option.
#!/bin/sh | |
echo "What should the Application be called (no spaces allowed e.g. GCal)?" | |
read inputline | |
name="$inputline" | |
echo "What is the url (e.g. https://www.google.com/calendar/render)?" | |
read inputline | |
url="$inputline" |