create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
This playbook has been removed as it is now very outdated. |
#-----------------------------------------------# | |
# oathtool totp google 2 factor | |
#-----------------------------------------------# | |
# if you have already set up 2 factor authentication with your phone | |
# you need to remove it from your phone and google authenticator app | |
# this wont invalidate your backup codes or application codes | |
# login to your google account go to 2 factor authentication, |
This gist contains the nginx and tor configurations for the [mike.tig.as][mta] servers, mainly to show:
chris-lea/nginx-devel
PPA to allow use of SPDY.ssl_ciphers
selection to mitigate BEAST attack, enable
[perfect forward secrecy][pfs] if possible and select the strongest
possible ciphers within those bounds. (Exception is made for several
ciphers at the end of list, for compatibility reasons.)org_posts_dir = "org_posts" # directory under source | |
# From http://www.ewal.net/2012/09/08/octopress-customizations/ | |
# Modified to have default flag of true to include drafts | |
desc "Rename files in the posts directory if the filename does not match the post date in the YAML front matter" | |
task :rename_posts do | |
rename_posts_in_dir "#{source_dir}/#{posts_dir}", "markdown" | |
# remove next line if you're you're not using org-mode | |
rename_posts_in_dir "#{source_dir}/#{org_posts_dir}", "org" |
Video on this Gist: https://www.youtube.com/watch?v=zvpLDuRY4ss&feature=c4-overview&list=UUj8_147vA3FQ1quI_CjciIQ | |
#Initialize a bare repo on the webserver. This would preferably be outside of your public website dir but if you are on a shared host you may not have that option. I like to make a folder just outside of the live folder called git. So for me it would look like this… | |
$ cd /var/www | |
$ mkdir git && cd git | |
$ git init –-bare | |
#Now you need to create a post-receive hook that will check out the latest tree from the Git repo you just setup into the /var/www/html folder where you want your website to be. You can make this whatever folder you want your code to end up in. | |
#This will create a file called post-receive in the hooks dir of the git repo. |
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
# Basically the nginx configuration I use at konklone.com. | |
# I check it using https://www.ssllabs.com/ssltest/analyze.html?d=konklone.com | |
# | |
# To provide feedback, please tweet at @konklone or email [email protected]. | |
# Comments on gists don't notify the author. | |
# | |
# Thanks to WubTheCaptain (https://wubthecaptain.eu) for his help and ciphersuites. | |
# Thanks to Ilya Grigorik (https://www.igvita.com) for constant inspiration. | |
server { |
figlet "I've got something to say" | |
figlet -f thick "Make Tech ASCIIer" | |
date | figlet -f basic |