For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
| #!/bin/bash | |
| # cd into the directory | |
| cd ~/gitsync/github-wordpress-sync/; | |
| # Make sure we are not already running | |
| if [ -f .sync-running ];then | |
| if test ! `find ".sync-running" -mmin +10`;then | |
| # Currently running, but not stuck | |
| exit 1; | |
| fi | |
| fi; |
| require "pathname" | |
| namespace :deploy do | |
| task :create_symlink, :except => { :no_release => true } do | |
| deploy_to_pathname = Pathname.new(deploy_to) | |
| on_rollback do | |
| if previous_release | |
| previous_release_pathname = Pathname.new(previous_release) | |
| relative_previous_release = previous_release_pathname.relative_path_from(deploy_to_pathname) |
| #!/usr/bin/env bash | |
| echo ">>> Starting Install Script" | |
| # Update | |
| sudo apt-get update | |
| # Install MySQL without prompt | |
| sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password password root' | |
| sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root' |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| # The Roots theme by default does not check production assets into Git, so | |
| # they are not deployed by Capistrano when using the Bedrock stack. The | |
| # following will compile and deploy those assets. Copy this to the bottom of | |
| # your config/deploy.rb file. | |
| # Based on information from this thread: | |
| # http://discourse.roots.io/t/capistrano-run-grunt-locally-and-upload-files/2062/7 | |
| # and specifically this gist from christhesoul: | |
| # https://gist.github.com/christhesoul/3c38053971a7b786eff2 |
| # see the current limits | |
| $ sysctl -a | grep maxproc | |
| # increase it | |
| $ sudo sysctl -w kern.maxproc=xxxx | |
| $ sudo sysctl -w kern.maxprocperuid=xxx | |
| # run at startup | |
| $ sudo vim /etc/sysctl.conf |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| <?php | |
| function omit_twitter_script($provider, $url, $args) { | |
| //get the hostname of the oEmbed endpoint provider being called | |
| $host = parse_url($provider, PHP_URL_HOST); | |
| //check to see that hostname is twitter.com | |
| if (strpos($host, 'twitter.com') !== false) { | |
| //adding ?omit_script=true to oEmbed endpoint call stops the returned HTML from containing widgets.js | |
| $provider = add_query_arg('omit_script', 'true', $provider); | |
| } | |
| //return the $provider URL so the oEmbed can be fetched |
| // Update: Hey Folks - I've got a full Gulpfile with everything else over at https://github.com/wesbos/React-For-Beginners-Starter-Files | |
| var source = require('vinyl-source-stream'); | |
| var gulp = require('gulp'); | |
| var gutil = require('gulp-util'); | |
| var browserify = require('browserify'); | |
| var reactify = require('reactify'); | |
| var babelify = require('babelify'); | |
| var watchify = require('watchify'); | |
| var notify = require('gulp-notify'); |