anthonynsimon

#!/usr/bin/env bash

# Applies common security measures for Ubuntu servers. Run it before doing the inital deploy with basecamp/kamal
#
# Afterwards, you'll only be able to SSH into the server as 'nonroot', eg. nonroot@1.2.3.4
#
# So add this to your Kamal deploy.yml:
# ```
# ssh:
#  user: nonroot

rameerez

#!/bin/bash

# ─────────────────────────────────────────────────────────────────────────────
# Production Docker Host Setup & Hardening Script — v3.2.1
# For Ubuntu Server 24.04 LTS (Noble) and 26.04 LTS (Resolute)
# Suitable for both Kamal 2.x deployment hosts and remote builder hosts
#
# Part of RailsFast (https://railsfast.com) — free & open source, MIT licensed.
#
# Usage (as root, on a fresh server):

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

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

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.:

---

Log1x

<?php
/**
 * composer require sentry/sentry-sdk
 */

Env::init();

// ...

if (env('SENTRY_DSN') && env('WP_ENV') !== 'development') {

swalkinshaw

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

kellymears

<?php

/**
 * composer require sentry/sentry-sdk 
 */
use Sentry;

Env::init();

// Bedrock application config...

Xilonz

name: Deploy

on: [push]
        
jobs:
  deploy_staging:
    name: deploy to staging
    runs-on: ubuntu-latest
    container:
      image: itinerisltd/tiller:latest