mohakevin

#FOR MULTIPLE REDIS INSTANCE INSTALLATION ON RHEL7+ USE THE FOLLOWING PATHS AND SETUP PROCESS:

create a new redis .conf file

$ cp /etc/redis.conf /etc/redis-xxx.conf

edit /etc/redis-xxx.conf, illustrated as below

Git Cheat Sheet

Visit my blog or connect with me on Twitter

Commands

Getting Started

git init

or

Postmortem incidencia #Ticket-ID

Fecha

2016-10-16

Autores

Carlos
Adrián

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

Index:

AWS S3 bucket policy recipes

Anonymous GET access
Anonymous GET access - match HTTP referrer
Full access for specific IAM user/role
GET/PUT/DELETE access to specific path within a bucket
LIST/PUT/DELETE access to specific path within a bucket
Full access (and S3 console) for specific IAM users

Anonymous GET access

Type: bucket

Setting up a WordPress site on AWS

This tutorial walks through setting up AWS infrastructure for WordPress, starting at creating an AWS account. We'll manually provision a single EC2 instance (i.e an AWS virtual machine) to run WordPress using Nginx, PHP-FPM, and MySQL.

This tutorial assumes you're relatively comfortable on the command line and editing system configuration files. It is intended for folks who want a high-level of control and understanding of their infrastructure. It will take about half an hour if you don't Google away at some point.

If you experience any difficulties or have any feedback, leave a comment. 🐬

Coming soon: I'll write another tutorial on a high availability setup for WordPress on AWS, including load-balancing multiple application servers in an auto-scaling group and utilizing RDS.

	#!/bin/bash
	#
	# transcode-video.sh
	#
	# Copyright (c) 2013-2015 Don Melton
	#

	about() {
	cat <<EOF
	$program 5.13 of April 8, 2015

	#!/bin/bash
	#
	# This script configures WordPress file permissions based on recommendations
	# from http://codex.wordpress.org/Hardening_WordPress#File_permissions
	#
	# Author: Michael Conigliaro <mike [at] conigliaro [dot] org>
	#
	WP_OWNER=www-data # <-- wordpress owner
	WP_GROUP=www-data # <-- wordpress group
	WP_ROOT=$1 # <-- wordpress root directory

	# This is an annotated subset of the Nginx configuration from our Magento production platform @ www.hypernode.com
	# See https://www.byte.nl/blog/magento-cacheleak-issue

	# !!!! If you are a Hypernode customer, do not use this config as it will result in duplicate statements. !!!!!

	user app;
	worker_processes 4;
	pid /var/run/nginx.pid;

	events {

	# This is a template .gitignore file for git-managed WordPress projects.
	#
	# Fact: you don't want WordPress core files, or your server-specific
	# configuration files etc., in your project's repository. You just don't.
	#
	# Solution: stick this file up your repository root (which it assumes is
	# also the WordPress root directory) and add exceptions for any plugins,
	# themes, and other directories that should be under version control.
	#
	# See the comments below for more info on how to add exceptions for your