mpneuried

# import config.
# You can change the default config with `make cnf="config_special.env" build`
cnf ?= config.env
include $(cnf)
export $(shell sed 's/=.*//' $(cnf))

# import deploy config
# You can change the default deploy config with `make cnf="deploy_special.env" release`
dpl ?= deploy.env
include $(dpl)

tollmanz

# Install dependencies
# 
# * checkinstall: package the .deb
# * libpcre3, libpcre3-dev: required for HTTP rewrite module
# * zlib1g zlib1g-dbg zlib1g-dev: required for HTTP gzip module
apt-get install checkinstall libpcre3 libpcre3-dev zlib1g zlib1g-dbg zlib1g-dev && \

mkdir -p ~/sources/ && \

# Compile against OpenSSL to enable NPN

hhhonzik

# Kinsta Deployment through Github Actions for Bedrock/Sage.
# 
# Placed at: .github/workflow/deploy.yml
#
# Process should be studied from code, but some quick brief:
#  - runs composer / sage installation
#  - moves correct `.env.*` file for multiple configs
#  - uses rsync to sync files, uses /.rsyncignore file to exclude whatever should not be there
#  - symlinks uploads folder and symlink release folder to kinsta public hostname
#  - if you want to clear cache, please uncomment the last job

LukaGiorgadze

package ec

import (
	"crypto/ecdsa"
	"crypto/elliptic"
	"crypto/md5"
	"crypto/rand"
	"crypto/x509"
	"encoding/pem"
	"errors"

mindfullsilence

This script will create a roots/bedrock project in your desired directory, install composer dependencies, and install wordpress via the wp-cli tool. Works with mailhog.

For global homestead installations (not per-project installs)

Place the sh file in Homestead/scripts/site-types/

In your Homestead.yaml file, use "bedrock" as the type key for a site mapping, and the value of the map key as the database. Be sure to add /web to the end of your to: key for your folder mapping. The script will generate the web folder for you. E.g.:

---

claudiofahey

//
// Companion code to https://medium.com/statuscode/pipeline-patterns-in-go-a37bb3a7e61d
//
// To run:
//   go get github.com/pkg/errors
//   go run -race pipeline_demo.go
//

package main

alexanderadam

* Shows a message while asserting like: 

ok: [host] => {                  
    "msg": "disk usage 4.2B of total 20.0GB (21.0%) (should exceed limit 90.0%)"
}

* Note this only looks at first mount point on current node
* Fails if disk is near-full
* Last step pushes to a push-based monitoring service, which will alert us if it doesn't get there after some time
* Need to setup a  variable `disk_limit`, which is the max acceptable usage ratio, e.g. set it to 0.8 if you want to keep disks within 80% of max size

swalkinshaw

<?php
/**
 * composer require sentry/sentry-sdk 
 */
use Sentry;
Env::init();
// Bedrock application config...
if (env('SENTRY_DSN')) {
    Sentry\init([
        'dsn'         => env('SENTRY_DSN'),

motemen

#!/bin/sh

# usage: push-gh-pages DIRECTORY # DIRECTORY is where GitHub pages contents are in (eg. build)
# LICENSE: Public Domain

set -e

remote=$(git config remote.origin.url)
described_rev=$(git rev-parse HEAD | git name-rev --stdin)

strarsis

Object caching with Bedrock (and Trellis) using Redis

What is object caching

While nginx microcaching already solves page caching (as of static, rarely changing WordPress pages), the performance for dynamically generated pages (like WooCommerce shop pages and admin backend in general) can benefit greatly from additionally using an object cache. Object caching allows an application (in this case WordPress with its plugins, theme, etc.) to store prepared objects (mostly database queries) in a database and quickly retrieve them, therefore improving the performance of dynamic page generation. Object caching is (usually) transparent, which means that it shouldn't be noticeable by users and developers (except for the performance improvements of course).

Implementations