- Affects: Amasty (Product-) Feed (Magento 1)
- Date: 2016-07-20 (updated: 2016-07-26)
- Author: Jeroen Boersma
#/bin/sh | |
# Configurable | |
remote='origin'; | |
master='master'; | |
days=0; | |
unmerged=0; | |
eval set -- `getopt -l master: -l remote: -l days: -l help -l unmerged -- 'm:?r:?d:?u?h?' "$@"`; |
For docker I've some local scripts which I occasionaly use for day-to-day jobs. The reason I don't commit them in the repository is because they're so project specific.
- Install https://github.com/JeroenBoersma/docker-compose-development
bin/dev setup
- Put the scripts in
workspace/bin
with execute permissions.
#!/bin/bash | |
CWD=${PWD}; | |
aws() { | |
docker run --rm -it -v ${HOME}/.aws:/root/.aws -v ${CWD}:/mnt --workdir=/mnt amazon/aws-cli "$@" | |
return $?; | |
} | |
if [ -z "`which jq`" ]; then |
<?php | |
/** | |
* Cleanup images from Magento | |
*/ | |
require 'app/Mage.php'; | |
if (!Mage::isInstalled()) { | |
echo "Application is not installed yet, please complete install wizard first."; | |
exit; |
Magento root plugin doesn't work with the latest Magento 2.3.5-1 so you have to manualy compare the magento/project-communtiy-edtion
with your local installation. Added composer.json
below.
Head over to your project
# before you start, update all packages
composer update
# Switch Magento version
April 28th I've found a endpoint in a thirth party module Klaviyo Magento 2 which allows to read private customer data from stores. It works by reclaiming any guest-cart as your own and reading the private data for the orders in the Magento API.
- Date: April 28 2021
- Who: Jeroen Boersma
- Target: Klaviyo Magento 2 module
- Version: 1.0.0 and up - 2.1.0
- Fixed in: 3.0.0 (May 25 2021)
src: https://www.stationx.net/nmap-cheat-sheet
| Switch | Example | Description |
- Affects: Magento 1 - Amasty Feed
- Date: 2016-07-20
- Author: Jeroen Boersma jeroen@srcode.nl
Because Varnish doesn't support SSL, most people choose a setup where Nginx SSL will forward all traffic to Varnish and Varnish will forward will forward the traffic it cannot handle back to nginx. Or worse, bind Varnish on port 80 and direct all traffic into Varnish. This will already degrade performance, because Varnish will purge more because static files are also taking up room in the cache.
Next up, the Nginx configuration of Magento will handle static files.