mcnamee

# Installation ---
# 1. In Bitbucket, add FTP_USERNAME, FTP_PASSWORD and FTP_HOST as environment variables.
# 2. Commit this file (bitbucket-pipelines.yml) to your repo (in the repo root dir)
# 3. From Bitbucket Cloud > Commits > Commit Number > Run Pipeline > Custom:Init (this will
#    push everything and initialize GitFTP)
#
# Usage ---
# - On each commit to master branch, it'll push all files to the $FTP_HOST
# - You also have the option to 'init' (see 'Installation' above) - pushes everything and initialises
# - Finally you can also 'deploy-all' (from Bitbucket Cloud > Commits > Commit Number > Run Pipeline > Custom:deploy-all)

mcnamee

(function($) {
  // Which links should we prefetch?
  var $linkElements = $(".menu-item a");

  $linkElements.on("hover", function() {
      var link = $(this).attr("href"),
          prerenderLink = $("#prerenderLink");
      if (prerenderLink.length) {
          if (prerenderLink.attr("href") === link) return;
          prerenderLink.attr("href", link);

mcnamee

#
#
# Installs Magento2 "the Pivotal Way"
#
# Simply run the following from your CLI:
# `bash <(curl -s <URL TO THE 'RAW' VERSION OF THIS GIST>)`
#
# You get Magento2 installed and the Pivotal Theme
#
# Prereq's: Composer, WP-CLI, Git, Unix

mcnamee

How to install Node.js & NPM on CentOS with CloudLinux and CageFS

Add node.js yum repository

yum install -y gcc-c++ make
curl -sL https://rpm.nodesource.com/setup_14.x | sudo -E bash -

Install node.js and NPM

yum install nodejs

mcnamee

Clean up references to other node version packages

rm -f /etc/yum.repos.d/nodesource-el.repo
yum clean all

Remove Old Node version

mcnamee

<?php
/**
 * Fetches and Caches a Instagram Feed
 *
 * - Get an Instagram Developer Account here: https://www.instagram.com/developer/
 * - Create a new client, using the 'redirect URI' as https://rudrastyh.com/tools/access-token
 * - Get an access token here: https://rudrastyh.com/tools/access-token
 * - This file will return JSON - so use some AJAX on the front-end to display
 * - Add the instagram-feed-cache.json file as ignored, to .gitignore
 */

mcnamee

<?xml version="1.0"?>
<ruleset name="Pivotal Agency">
    <description>Pivotal Wordpress Coding Standards</description>

    <!-- Scan all files in directory -->
    <file>.</file>

    <!-- Scan only PHP files -->
    <arg name="extensions" value="php"/>

mcnamee

{
    "Statement": [
        {
            "Action": [
                "apigateway:*",
                "cloudformation:CancelUpdateStack",
                "cloudformation:ContinueUpdateRollback",
                "cloudformation:CreateChangeSet",
                "cloudformation:CreateStack",
                "cloudformation:CreateUploadBucket",

mcnamee

Using multiple GitHub deploy keys on a single server with a single user

Within GitHub it is possible to set up two types of SSH key - account level SSH keys and and repository level SSH keys. These repository level SSH keys are known in GitHub as deploy keys.

Deploy keys are useful for deploying code because they do not rely on an individual user account, which is susceptible to change, to “store” the server keys.

There is, however, an ‘issue’ with using deploy keys; each key across all repositories on GitHub must be unique. No one key can be used more than once. This becomes a problem when deploying to repositories to the same server with the same user. If you create two keys, the SSH client will not know which key to use when connecting to GitHub.

One solution is to use an SSH config file to define which key to use in which situation. This isn’t as easy as it seems.. you might try something like this:

mcnamee

pipelines:
  custom:
    # PHPCS
    # ---------------------------------------------------------------
    phpcs:
    - step:
        image: edbizarro/gitlab-ci-pipeline-php:7.4-alpine
        caches:
          - composer
        script: