Sangseng Lee epicsagas

Mac OS X LEMP Configuration

This Gist is a collection of configuration files that can be used to easily setup a Homebrew-based LEMP stack on Mac OS X.

Files in this repository are numbered and named for ordering purposes only. At the top of each file is a section of metadata that denote what component the file belongs to and the default name & location of the file. Feel free to implement it however you want.

Note: some configuration files have hard-coded paths to my user directory -- fix it for your setup

Setup

It seems that it does not matter what timezone is on the server as long as you have the time set right for the current timezone, know the timezone of the datetime columns that you store, and are aware of the issues with daylight savings time.

On the other hand if you have control of the timezones of the servers you work with then you can have everything set to UTC internally and never worry about timezones and DST.

Here are some notes I collected of how to work with timezones as a form of cheatsheet for myself and others which might influence what timezone the person will choose for his/her server and how he/she will store date and time.

MySQL Timezone Cheatsheet

Default

Powerlevel10k

Works for macOS Sierra and High Sierra

Taken from 2011 Macbook Pro Graphics Card FIX 100% WORKING!!!

EDIT This method works! But there is an improved version for better thermal management and brightness keys functionality. See improved version -> https://gist.github.com/cdleon/d1eff7246a25193304284ecec40445b0

Enter Recovery Mode (text mode)

if you are on high sierra 10.13.6+ you might need to use Command + r instead

Boot up holding down Command + r + s

Remove MySQL completely

Open the Terminal
Use mysqldump to backup your databases
Check for MySQL processes with: ps -ax | grep mysql
Stop and kill any MySQL processes
Analyze MySQL on HomeBrew:

brew remove mysql

Login with account user (not root)

mkdir pem
cd pem
ssh-keygen -b 2048 -f identity -t rsa

Copy public key contents to authorized_keys

	function createKoreanWon($price = 0)
	{
	$krw = '';

	if($price) {
	$priceArr = str_split(strrev((string)$price), 4);

	$unitArr = ['','만','억','조','경'];
	$count = min(count($priceArr),count($unitArr));

	!#/bin/bash
	# commands are from https://tecadmin.net/laravel-file-permissions/

	user=$1
	group=$2
	dir=$3

	chown -R $1:$2 $3;
	find $dir -type f -exec chmod 644 {} \;
	find $dir -type d -exec chmod 755 {} \;

	#!/usr/bin/env php
	<?php
	// locate this {project root}/.git/hooks/pre-commit)
	// and make this runnable with chmod +x
	echo "Running tests.. ";
	exec('vendor/bin/phpunit', $output, $returnCode);
	if ($returnCode !== 0) {
	// Show full output
	echo PHP_EOL . implode($output, PHP_EOL) . PHP_EOL;
	echo "Aborting commit.." . PHP_EOL;

	Source: https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster

	innodb_buffer_pool_size = 4G
	innodb_log_buffer_size = 256M
	innodb_log_file_size = 1G
	innodb_write_io_threads = 16
	innodb_flush_log_at_trx_commit = 0
	Why these settings ?

	innodb_buffer_pool_size will cache frequently read data