grafikchaos

# in your aliases
# make sure your git-create-branch.sh is executable -> chmod +x path/to/your/git-create-branch.sh
alias gcb='path/to/your/git-create-branch.sh'

grafikchaos

# in your aliases 
# (make sure your git-destroy-branch.sh is executable -> chmod +x path/to/your/git-destroy-branch.sh)
alias git-delete-branch='path/to/your/git-destroy-branch.sh'

grafikchaos

Basic pre-requisites

• Some utilities:

sudo apt-get install vim tmux git

• Copy/paste from the command line:

sudo apt-get install xclip

grafikchaos

Installing git on CentOS 5 using yum

Since you're using CentOS 5, the default package manager is yum, not apt-get. To install a program using it, you'd normally use the following command:

$ sudo yum install <packagename>

However, when trying to install git this way, you'll encounter the following error on CentOS 5:

grafikchaos

# ~/.oh-my-zsh/custom/aliases.zsh

# At the end of the file you can add the aliases from above 
# or any other ones you find useful
alias ..='cd ..'
alias ll='ls -alGhF'
alias install='sudo apt-get install'
alias upgrade='sudo apt-get upgrade'
alias update='sudo apt-get update'
alias search='sudo apt-cache search -n'

grafikchaos

<?xml version="1.0" encoding="UTF-8" ?>

<!--
 This is the Solr schema file. This file should be named "schema.xml" and
 should be in the conf directory under the solr home
 (i.e. ./solr/conf/schema.xml by default)
 or located where the classloader for the Solr webapp can find it.

 For more information, on how to customize this file, please see
 http://wiki.apache.org/solr/SchemaXml

grafikchaos

curl http://localhost:8484/solr/core0/update\?commit\=true -d  '<delete><query>*:*</query></delete>'

grafikchaos

How to make unoconv run inside an apache instance: CHEAT

First, you should read this stackoverflow post

The instructions below are slightly modified to a specific project where we're converting every document to PDF

---

Create the /usr/local/bin/unoconv.sh file

grafikchaos

Overview

This is the process I have found to be very helpful when migrating projects from their SVN repository over to Git. When migrating from one version control system to another it's important to retain as much information about the development history as possible (i.e., commit messages, tags, branches, etc.) and avoid the easy and tempting method of just downloading the project from a server and throw it into the new version control (you should only consider that if the project has never been in a version control system before).

Key concepts:

• tools for migrating svn repositories to git
• how to migrate standardized svn repositories
• how to migrate non-standardized svn repositories
• best practices for your now un-maintained SVN repository

grafikchaos

Before you begin

Read Aaron Hawks' blog post for the original idea for this gist.

While this process should theoretically work to upgrade the core/default files that come with Magento from any old version to the most recent version (as long as they're in the same distribution, i.e., Community to Community or Enterprise to Enterprise), you should always refer to Magento's release notes and upgrade paths for the version you're upgrading to for full details and work flow. This is the process I used to go from Magento EE 1.12.0.2 to Magento EE 1.13.0.1 directly ( skipping over 1.13.0.0 due to the instructions outlined in this Magento article and release notes ).

---

Upgrade Pre-Requisites