dzungtran

package main

import (
	"fmt"
	"go.uber.org/dig"
)

type Say struct {
	Name string
}

dzungtran

package main
// Sample file for test: https://drive.google.com/file/d/1DFkJdX5UTnB_xL7g8xwkkdE8BxdurAhN/view?usp=sharing
import (
	"encoding/csv"
	"encoding/json"
	"fmt"
	"io"
	"os"
	"strconv"
	"sync"

dzungtran

GIT_TAG='v1.1.0'
go get -d -u github.com/golang/protobuf/protoc-gen-go
git -C "$(go env GOPATH)"/src/github.com/golang/protobuf checkout $GIT_TAG
go install github.com/golang/protobuf/protoc-gen-go

Check current protoc-gen-go location

dzungtran

Create request logging server on local (for testing purpose)

• Create index.php
• Start php built-in server on local by command: php -S localhost:8000
• Publish local server to serveo: ssh -o ServerAliveInterval=60 -R 80:localhost:8000 serveo.net

dzungtran

# Clean, simple, compatible and meaningful.
# Tested on Linux, Unix and Windows under ANSI colors.
# It is recommended to use with a dark background.
# Colors: black, red, green, yellow, *blue, magenta, cyan, and white.
#
# Mar 2013 Yad Smood

# VCS
YS_VCS_PROMPT_PREFIX1=" %{$fg[white]%}on%{$reset_color%} "
YS_VCS_PROMPT_PREFIX2=":%{$fg[cyan]%}"

dzungtran

# USER GUIDE:
# Do not run this script directly

# Compress multiple folders, each into its own zip archive
# BEGIN
for i in */; do zip -r "${i%/}.zip" "$i"; done
# OR
for i in *
do
[ -d "$i" ] && zip -r "$i.zip" "$i"

dzungtran

input {
	
	#logstash -f logstash.conf < request.log > output.txt
	stdin {
		type => "laravel_logs"
		codec => multiline {
	        	pattern => "^\["
			what => "previous"
			negate => true
	    	}

dzungtran

#!/bin/bash

if [ ! -f ./app/etc/local.xml ]; then
    echo "-- ERROR"
    echo "-- This doesn't look like a Magento install.  Please make sure"
    echo "-- that you are running this from the Magento main doc root dir"
    exit
fi

if [ `id -u` != 0 ]; then

dzungtran

Before you do anything

• Make sure you test clearing this data in a non-production environment first.
• Always make backups before you lose data forever.
• Make sure you're truncateing, not droping.
• Probably a good idea to reindex everything via shell after mass deleting records

---

To expand on Jim's answer, Magento Support doesn't need the contents of these tables when they ask for a copy of your DB, so you could consider them non-essential.

dzungtran

SET foreign_key_checks = 0;
TRUNCATE dataflow_batch_export;
TRUNCATE dataflow_batch_import;
TRUNCATE log_customer;
TRUNCATE log_quote;
TRUNCATE log_summary;
TRUNCATE log_summary_type;
TRUNCATE log_url;
TRUNCATE log_url_info;
TRUNCATE log_visitor;