esamattis

# -----------------------------------------------------------------
# .gitignore for WordPress
# Bare Minimum Git
# http://ironco.de/bare-minimum-git/
# ver 20150227
#
# This file is tailored for a WordPress project 
# using the default directory structure
#
# This file specifies intentionally untracked files to ignore

pylover

#! /usr/bin/env python3
"""Fixing bluetooth stereo headphone/headset problem in debian distros.

Workaround for bug: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197
Run it with python3.5 or higher after pairing/connecting the bluetooth stereo headphone.

This will be only fixes the bluez5 problem mentioned above .

Licence: Freeware

rgl

bash -c 'while [[ "$(curl -s -o /dev/null -w ''%{http_code}'' localhost:9000)" != "200" ]]; do sleep 5; done'

# also check https://gist.github.com/rgl/c2ba64b7e2a5a04d1eb65983995dce76

apphands

git filter-branch -f --index-filter 'git rm -r -f --ignore-unmatch <FILE_TO_REMOVE>' HEAD

ethicka

#!/bin/bash -e

##
# WordPress Installation and VirtualHost Creation
#
# Description: Installs a WordPress website in the ~/Sites folder, creates a homepage, 
# cleans up the WP install a bit, deletes the akismet and hello dolly plugins, creates the permalinks, 
# clones the roots/sage theme framework to the theme folder, deletes all the other WP default themes, 
# installs/runs npm and bower and runs gulp to create the initial assets, adds a custom gitignore file 
# to /wp-content, installs the roots/soil plugin, creates a git repo in wp-content, saves the WordPress 

davestevens

Let's Encrypt

Examples of getting certificates from Let's Encrypt working on Apache, NGINX and Node.js servers.

Obtain certificates

I chose to use the manual method, you have to make a file available to verify you own the domain. Follow the commands from running

git clone https://github.com/letsencrypt/letsencrypt
cd letsencrypt

Soreine

{% if site.disqus_short_name and page.comments != false %}
<div id="disqus_thread"></div>
<script>
 var disqus_shortname = '{{ site.disqus_short_name }}';
 var disqus_config = function () {
   // _config.yml should define the site's URL
   this.page.url = '{{ site.url }}{{ page.url }}';
   // Using an optional disqus_identifier variable, or the site.url + page.id combination
   this.page.identifier = '{% if page.disqus_identifier %}{{ page.disqus_identifier}}{% else %}{{ site.url }}{{ page.id }}{% endif %}';
 };

cadebward

import mongoose, {Schema} from 'mongoose'

export const ServiceSchema = new Schema({
  displayName: {type: String, required: true, unique: true}
})

ServiceSchema.set('toObject', {
  transform: function (doc, ret) {
    ret.id = ret._id
    delete ret._id

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

phlbnks

#!/bin/bash -e
clear
echo "============================================"
echo "WordPress Install Script"
echo "============================================"
echo "Do you need to setup new MySQL database? (y/n)"
read -e setupmysql
if [ "$setupmysql" == y ] ; then
	echo "MySQL Admin User: "
	read -e mysqluser