Raul Watson diazwatson

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

Purpose

The purpose of this SQL script is to clean up a Magento 1.x database by deleting orphaned records from database tables which cause foreign key contraint failures. This happens when at some point in time records where deleted from the database while FOREIGN_KEY_CHECKS = 0 and the person performing the delete operations failed to delete all related records pertaining to related tables of the primary table.

This script can be helpful when encountering foreign key constraint failures using the Data Migration Tool to migrate your

Use both files in your root folder and run:

curl -LO https://deployer.org/deployer.phar && sudo mv deployer.phar /usr/local/bin/dep && sudo chmod +x /usr/local/bin/dep
composer require deployer/recipes --dev
composer require rafaelstz/deployer-magento2 dev-master --dev

To patch code in Composer modules

composer require cweagans/composer-patches
Create your patch file as normal (referencing the paths to file in /vendor) and put it in a '.patches' folder at the top level of your code base.
Edit composer.json to apply the patch(es) as below (this goes at the first level of composer.json) :

    "extra": {
        "magento-force": "override",
        "enable-patching": true,
        "patches-file": "composer.patches.json"
 },

	# Source : http://thezinx.com/2013/10/29/create-bootable-dmg-iso-mavericks-app.html

	# Mount the installer image
	hdiutil attach /Applications/Install\ OS\ X\ Mavericks.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app

	# Convert the boot image to a sparse bundle
	hdiutil convert /Volumes/install_app/BaseSystem.dmg -format UDSP -o /tmp/Mavericks

	# Increase the sparse bundle capacity to accommodate the packages
	hdiutil resize -size 8g /tmp/Mavericks.sparseimage

	#####################################################
	#
	# Provided by the Magento Support Center
	# http://magentosupport.help/knowledgebase/configuring-nginx-to-work-with-magento-advanced/
	#
	# Your Magento Tutorial specialists
	#
	server {
	listen *:8080;
	server_name fanatik.redrokk.com www.fanatikbike.com fanatikbike.com;

	$ git remote rm origin
	$ git remote add origin [email protected]:aplikacjainfo/proj1.git
	$ git config master.remote origin
	$ git config master.merge refs/heads/master

	# To be pasted in ~/.profile
	vagrant() {
	if [[ $@ == "halt all" ]]; then
	command vagrant global-status \| grep running \| colrm 8 \| xargs -L 1 -t vagrant halt
	else
	command vagrant "$@"
	fi
	}

	-- MySQL dump 10.13 Distrib 5.7.19-17, for debian-linux-gnu (x86_64)
	--
	-- ------------------------------------------------------
	-- Server version 5.7.19-17

	/!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /;
	/!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS /;
	/!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION /;
	/!40101 SET NAMES utf8 /;
	/!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE /;

	{
	"info": {
	"_postman_id": "ac491bb7-de4a-4258-b717-ba80070f50fe",
	"name": "Magento",
	"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
	},
	"item": [
	{
	"name": "Mine / Me",
	"item": [