⌘T | go to file |
⌘⌃P | go to project |
⌘R | go to methods |
⌃G | go to line |
⌘KB | toggle side bar |
⌘⇧P | command prompt |
#!/bin/bash | |
# | |
# This is the script responsible for updating our Puppet master data, | |
# which includes modules, manifests, hiera data, etc. All of this data is | |
# managed in a git repository and upon "deploy" it is synced into the Puppet | |
# master. | |
# | |
# This script mirrors the remote git repository, looking for branches that | |
# match "env-*" (such as "env-production" or "env-test"). Each of these branches | |
# is setup as an environment into the Puppet master's data files. The |
From the Apache Software Foundation, "Solr is an open source enterprise search server based on the Lucene Java search library, with XML/HTTP and JSON, Ruby, and Python APIs, hit highlighting, faceted search, caching, replication, and a web administration interface." Magento has had built-in support for Solr since Enterprise verion 1.8.
The following instructions show how to complete a basic installation and configuration of Apache Solr for use with Magento Enterprise on CentOS/RHEL 6. These instructions the Java JDK with Tomcat rather than jetty.
Note: Solr should be on a dedicated server if possible, especially for large installations, as it can be resource intensive
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 ).
# This is a skeleton for testing models including examples of validations, callbacks, | |
# scopes, instance & class methods, associations, and more. | |
# Pick and choose what you want, as all models don't NEED to be tested at this depth. | |
# | |
# I'm always eager to hear new tips & suggestions as I'm still new to testing, | |
# so if you have any, please share! | |
# | |
# @kyletcarlson | |
# | |
# This skeleton also assumes you're using the following gems: |
ALTER TABLE `enterprise_url_rewrite_redirect` | |
ADD INDEX `redirect_id` (`redirect_id`) ; | |
ALTER TABLE `enterprise_url_rewrite` | |
ADD INDEX `request_path` (`request_path`) ; |
language: php | |
# | |
# Important to note, this is the version of PHP used to run this build, not the | |
# one used to run your Drupal installation. Ensure compatibility with the Drush | |
# and Terminus versions you're using for this build. | |
# | |
php: | |
- 5.3 |
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
# The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited | |
# | |
# Current known FCC address ranges: | |
# https://news.ycombinator.com/item?id=7716915 | |
# | |
# Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft | |
# | |
# In your nginx.conf: | |
location / { |