- version 3.6
Check those constraints:
$this->anything()
_complete_ssh_hosts () | |
{ | |
COMPREPLY=() | |
cur="${COMP_WORDS[COMP_CWORD]}" | |
comp_ssh_hosts=`cat ~/.ssh/known_hosts | \ | |
cut -f 1 -d ' ' | \ | |
sed -e s/,.*//g | \ | |
grep -v ^# | \ | |
uniq | \ | |
grep -v "\[" ; |
#!/bin/sh | |
head -n 4096 /dev/urandom | openssl sha1 |
# This is a template .gitignore file for git-managed WordPress projects. | |
# | |
# Fact: you don't want WordPress core files, or your server-specific | |
# configuration files etc., in your project's repository. You just don't. | |
# | |
# Solution: stick this file up your repository root (which it assumes is | |
# also the WordPress root directory) and add exceptions for any plugins, | |
# themes, and other directories that should be under version control. | |
# | |
# See the comments below for more info on how to add exceptions for your |
# For a symfony application to work properly, you MUST store this .htaccess in | |
# the same directory as your front controller, index.php, in a standard symfony | |
# web application is under the "public" project subdirectory. | |
# Use the front controller as index file. | |
DirectoryIndex index.php | |
# Uncomment the following line if you install assets as symlinks or if you | |
# experience problems related to symlinks when compiling LESS/Sass/CoffeScript. | |
# Options +FollowSymlinks |
<!-- | |
You can't do position absolute + visibility/opacity in gmail | |
display: none; only works if you inline it as !important, but then this destroys the functionality for | |
all other clients, this workaround has been working wonders for us!!! | |
--> | |
<style> | |
div.gmail { | |
display: block; | |
width: 0; | |
overflow: hidden; |
<?php | |
use Symfony\Component\HttpFoundation\Response; | |
use Symfony\Bundle\FrameworkBundle\Controller\Controller; | |
class CsvController extends Controller | |
{ | |
/** | |
* Get a CSV file from an array |
It sometimes happen you need change code on a machine from which you cannot push to the repo.
You’re ready to copy/paste what diff
outputs to your local working copy.
You think there must be a better way to proceed and you’re right. It’s a simple 2 steps process:
1. Generate the patch:
git diff > some-changes.patch
If you do, or want to, use AWS to deploy your apps, you will end up using AWS SES via SMTP when you're launching an app that sends out emails of any kind (user registrations, email notifications, etc). For example, I have used this configuration on various Ruby on Rails apps, however, it is just basic SMTP configurations and crosses over to any framework that supports SMTP sendmail.
There are two ways to go about this:
Luckily, you found this MD file and the NOT SO EASY WAY is suddenly copy-pasta... sudo yum....