pajtai

#!/usr/bin/env bash

# source: http://superuser.com/a/224263/41059
# OpenSSL requires the port number.
SERVER=$1:443

DELAY=1
echo Obtaining cipher list from $(openssl version).
ciphers=$(openssl ciphers 'ALL:eNULL' | sed -e 's/:/ /g')

pajtai

        {
            role: 'admin',
            enabled: true,
            firstname: 'Test',
            lastname: 'User',
            identities: {
                basic: {
                    username: 'admin',
                    salt: '225384010328',
                    hash: '885f59a76ea44e1d264f9da45ca83574fbe55e3e7e6c51afe681730b45c7bb03'

pajtai

add_action('atom_entry', 'add_thumbnail_to_feed');
add_action('rdf_item', 'add_thumbnail_to_feed');
add_action('rss_item', 'add_thumbnail_to_feed');
add_action('rss2_item', 'add_thumbnail_to_feed');
function add_thumbnail_to_feed(){
    global $post;
    if ( has_post_thumbnail( $post->ID ) ){
        $thumb = wp_get_attachment_image_src( get_post_thumbnail_id($post->ID), 'thumbnail' );
        $url = $thumb['0'];
        echo "<thumbnail>$url</thumbnail>";

pajtai

select
  option(selected disabled) Pick your country
  option(value='US') United States
  option(value='AF') Afghanistan
  option(value='AX') Åland Islands
  option(value='AL') Albania
  option(value='DZ') Algeria
  option(value='AS') American Samoa
  option(value='AD') Andorra
  option(value='AO') Angola

pajtai

#!/usr/bin/env bash
#set -x # for debugging

SSH_HOST="user@www.sample.com"

# using -f and -o exitOnForwardFailure is helpful, but if you are managing processes that restart and you want to keep
#   the tunnel open even after a restart this can be difficult (e.g. nodemon with a remote mongo, mysql, elasticsearch, etc)
#
# instead you can open the tunnels and close them on script exit

pajtai

server {
    listen 80;
    server_name example.com;

    location /analytics {
        auth_basic "Restricted Access";
        auth_basic_user_file /etc/nginx/htpasswd.users;
        # the only tricky part is that kibana won't work without the rewrite rule
        # to proxy from another port and use "location /", you can leave out the rewrite rules
        rewrite ^/analytics(.*)$ $1 break;

pajtai

Debugging node running on a remote server

Node uses a TCP interface for debugging, so if you can get a handle on the right port, you can debug apps running remotely. This means you can run through code on staging, Vagrant, etc. The following shows you how to start node with the debug flag and use an SSH tunnel to access the right port.

Things you need:

• ssh access to the server
• ability to restart node app with --debug flag or node-inspector installed on server

Debugging using Webstorm

pajtai

#!/usr/bin/env bash
set -e
#set -x # for debugging

# daily backups with logs crontab -e example:
# 0 1 * * * /home/user/path/to/this/file -u my-user -p 'my-pw' -d mydb -t 90 >>/home/user/logs/backup.log 2>&1

    MONGO_PW=""
    TTL=180

pajtai

#!/usr/bin/env bash
set -e
#set -x # for debugging

    MYSQL_PW=""
    TTL=365

    while test $# -gt 0; do
        case "$1" in
            -h|--help)

pajtai

I tested the following script on a vagrant box.

The box was 850MB without the script, and 450 MB with the script.

The script was taken from chef/bento with just one modification.