Hugo Dias hugodias

<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>

<general_guidelines>

NEVER use meta-phrases (e.g., "let me help you", "I can see that").
NEVER summarize unless explicitly requested.
NEVER provide unsolicited advice.
NEVER refer to "screenshot" or "image" - refer to it as "the screen" if needed.
ALWAYS be specific, detailed, and accurate.

Siteground (incident #1)

Date

2018-11-22

Authors

Hugo

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

Setting up and installing rbenv, ruby-build, rubies, rbenv-gemset, and bundler

This guide enables you to install (ruby-build) and use (rbenv) multiple versions of ruby, isolate project gems (gemsets and/or bundler), and automatically use appropriate combinations of rubies and gems.

TL;DR Demo

# Ensure system is in ship-shape.

aptitude install git zsh libssl-dev zlib1g-dev libreadline-dev libyaml-dev

agnoster.zsh-theme

forked by rjorgenson

A ZSH theme optimized for people who use:

Solarized
Git
Unicode-compatible fonts and terminals (I use iTerm2 + Menlo)
NVM
RVM

	<script type="application/ld+json">
	{
	"@context": "http://schema.org",
	"@type": "Organization",
	"@id": "#organization",
	"name": "Outlyer",
	"url": "https://www.outlyer.com/",
	"sameAs": [
	"https://github.com/outlyerapp",
	"https://twitter.com/outlyer",

	#!/bin/bash

	mkdir wordpress-site && cd wordpress-site

	touch docker-compose.yml

	cat > docker-compose.yml <<EOL
	version: "2"
	services:
	my-wpdb:

	# Sidekiq interaction and startup script
	commands:
	create_post_dir:
	command: "mkdir -p /opt/elasticbeanstalk/hooks/appdeploy/post"
	ignoreErrors: true
	files:
	"/opt/elasticbeanstalk/hooks/appdeploy/post/50_restart_sidekiq.sh":
	mode: "000755"
	owner: root
	group: root

	#!/usr/bin/env bash
	. /opt/elasticbeanstalk/support/envvars
	DIR=/var/app/current
	if [ "$WORKER_MODE" = "1" ]
	then
	if [ -f /var/run/shoryuken.pid ]
	then
	su -l -c "kill -USR1 `cat /var/run/shoryuken.pid`" root \|\| echo "no process"
	su -l -c "rm -f /var/run/shoryuken.pid" root \|\| echo "no file"
	fi

	SELECT
	date_trunc('month', ph1.created_at) AS date,
	SUM(SUM(ph2.after - ph2.before))
	OVER (
	ORDER BY date_trunc('month', ph1.created_at)) AS mrr,
	SUM(CASE WHEN ph1.event = 'new'
	THEN (ph1.after - ph1.before)
	ELSE 0 END) AS new,
	SUM(CASE WHEN ph1.event = 'upsell'
	THEN (ph1.after - ph1.before)