Shyim's Brain

Building PHP docker images in a better way with Wolfi-OS

Sat, 06 Apr 2024 23:00:00 +0000

⚠️ DEPRECATED: DO NOT USE THIS APPROACH ANYMORE

This blog post contains outdated information. Chainguard has significantly reduced its commitment to open source, and the wolfiphp approach described here is no longer recommended for production use. See the wolfiphp announcement for more details.

Alternative: Use Debian’s official packages with apt-get install php8.4-cli and related packages. While images may be larger, Debian provides stable, openly maintained PHP packages without dependency on corporate-controlled initiatives.

Building your Shopware project in the CI using shopware-cli

Mon, 21 Aug 2023 23:00:00 +0000

In this short blog post, I will show you how you can use shopware-cli to build your Shopware project and deploy it later with Deployer, Docker image whatever you want.

But first what is Shopware-CLI?

Shopware-CLI is a command line application written in Go. It’s not the same application as bin/console in your Project. It’s kinda a Swiss knife for the Shopware ecosystem. Likewise, it can do a lot of things like:

Devenv: Compose a Developer Environment easily for PHP with Nix

Sun, 25 Dec 2022 00:00:00 +0000

I have been using Nix for almost four years and also maintaining some packages at nixpkgs (the primary Nix repository). The Nix learning curve is complicated, so I could not get my colleagues into it. But Devenv made it so easy to compose a developer environment, so I got their attraction, and some of them switched already, and we are looking to where we can use it too.

What is Devenv?

Devenv allows you to describe in the Nix language how your project setup has to look like for any Unix-based systems (WSL2, Mac, Linux) for amd64/arm64 architectures. As you may know, no project has the same dependencies: one needs NodeJS 16, and the other NodeJS 18 already. For those reasons, there are already solutions like NVM(node version manager) where you can pin the version using a .nvmrc file. This works, of course, only for Node, and there are similar tools for any language and devenv allows you here to pin any package and with services.

How to build your Shopware extension assets much faster

Thu, 15 Dec 2022 21:00:00 +0000

When you deliver your Shopware extension to a Shop owner, your extension must contain in src/Resources/public the build assets for the Administration and the Storefront. We committed in the first plugins in Frosh all assets directly in Git. But this led to annoying conflicts, or when you merged two pull requests at once, it didn’t contain both changes.

So, for this reason, we removed the build files from all Git repositories again and used shopware-cli to build the files.

Easy and Cheap Shopware App Hosting using Cloudflare Workers

Sun, 27 Nov 2022 20:00:00 +0000

Shopware Apps are a different way to extend Shopware and can use an optional external App Server to provide additional functionality from your external backend. In this Blog post, I want to show you that a Shopware App with a Backend can be easy and also very affordable.

The scary backend server

Before the App system, the only way to extend Shopware was to build a plugin. Plugins are like Symfony Bundles with Shopware magic to offer them in Shopware Store. So we wrote code that runs directly in the customer’s web shop, and we can create additional tables to store our information. But we have to make sure that our code works on many setups and PHP versions. As the plugins can do like anything and this makes sandboxing difficult or build reliable that they don’t break each other. That was when the Shopware app system was born to offer a different extension concept.

Two weeks after using Gitpod only for development

Mon, 17 Oct 2022 18:00:00 +0000

I am working together with pumpi on a project named shopmon (will be announced when it’s done) and he is lazy to set up a local development environment, and I was lazy to show him that. So I gave him an instance of VS Code running on Web on my personal VPS. Everything was fine until I broke somehow IPv6 networking with Docker containers (I really hate networking), so we looked for an alternative.

How we do nightly automated load tests at Shopware

Thu, 26 May 2022 20:00:00 +0000

With the Shopware version 6.4.11.0, we improved the performance overall a lot. To make sure that we still improve, we decided to set up a nightly load testing job to ensure that the application performance stays the same. So we have running since a month an automated load test for Shopware 6 running, and in this post, I want to speak about it. To test the Shopware, we use multiple dedicated Cloud Servers from Hetzner Cloud and wrote some custom tooling around Ansible to spawn the servers before.

Shopware Rector Project

Tue, 17 May 2022 15:20:00 +0000

Last week I attended the first Hockethon (combination of Hackathon + Hockenheim) of the Kellerkinder. That event was unique, and I want to thank Kellerkinder for organizing such an event. If you are interested in what we all did on that event, check out the blog post from Marco

I teamed up with Manuel we made pretty fast progress to enable HTTP caching in the store-API. As the Storefront already has HTTP caching, we used the same logic. But in the end, we had a reference in the Core store-API to the HTTP cache of the storefront bundle. So to do it right, we had to extract the HTTP cache logic of Storefront into the core component. While migrating code between two components, we thought this task is so brain-dead, so let’s use Rector to do this for us.

A deep dive into Shopware 6 Caching

Mon, 02 May 2022 00:00:00 +0000

In this blog post, I want to dive into the Shopware Caching to clarify how it works and what you have to care about while developing features. We will go from the inner to the outer caching layer in multiple steps and look into them independently.

Stage one - the object cache

First, we will start with the object cache implemented in serval “route” classes. The “route” classes/controllers are always used in the Shopware context as an entry point for the store-API. These are controllers and services simultaneously, so the default storefront and the store-API can share the same code.

Easy and fast local Shopware 6 Development on Mac with Symfony CLI

Sun, 27 Feb 2022 00:00:00 +0000

I switched a month ago to macOS as of the M1 hype and wanted to try out the entire Apple ecosystem when I have an iPhone, iPad, and Mac. To get Shopware 6 running, I looked into some Guides for Mac and found out for myself: Why is this all so complicated, and why the hell is anyone using Docker for that.

Docker on Mac

I saw that many people are using Dockware for their Setup. (Dockware is a Docker image with all the Tools/Servers included to run Shopware 6). Docker runs not native on macOS and uses a Virtual machine to emulate a Linux kernel and all the containers below it. So obviously, the filesystem would be slow, and many people using, for this reason, SFTP or other tools like docker-sync to hold the same state between host and container. This is one of the most significant disadvantages for me. Like me, the dumb user has to run a tool to have this synchronized. I know that tools like PhpStorm can do this for me automatically, but when it doesn’t work, I will waste so much time to find this out.

Shopware packages is live + deprecation of packages.friendsofshopware.com

Wed, 01 Sep 2021 00:00:01 +0000

Today is finally the day when Shopware packages is being released. You might ask what is Shopware packages, and what does it have to do with packages.friendsofshopware.com? Good question 🙂

What is Shopware packages?

Shopware packages is the long-awaited official Composer package repository for all Shopware store extensions. But why do we want to use that or care about that?

What can I expect from Shopware packages?

With composer, we can manage all dependencies in our Shopware setups. We usually use a composer project template which requires Shopware and provides some basic tooling. When we want now update the Shopware version, we just pick a newer version of Shopware in composer, and we are ready to go. That’s nice and easy for our Shopware upgrades, but we mostly also use extensions for our shops such as PayPal. Typically, we download the ZIP-file from the Store, unpack and upload it to custom/plugins. Yes, we all are lazy and this really sounds annoying. With the new repository, we can treat the extensions as normal composer dependency like just using composer req store.shopware.com/swagpaypal like cool guys 😎. This will automatically get the most recent version compatible to our Shopware version and other requirements set by the extension manufacturer. Since the dependencies are built directly into Composer, we can use typical commands like composer update store.shopware.com/swagpaypal to update the extension or even update Shopware and all required extensions at once. It’s cool, isn’t it?

Optimization of Thumbnails in PHP

Wed, 14 Jul 2021 00:15:59 +0000

Every shop owner wants a fast online shop with the best pagespeed results. The images have a huge impact on these stats. But can we achieve better results with only PHP?

Image generation with PHP

In PHP there are two ways how images can be generated: using the gd, or the ImageMagick extension. Both extensions are not optimized to create very small images and they are quite slow. They also lack support for newer image formats like avif (PHP 8.1 will have avif in gd). The PHP community has build packages (like spatie/image-optimizer) to optimize an image after it has been uploaded by executing several optimziers in the CLI. This approach requires to have functions like exec, system or proc_open available, which are disabled by default on some shared hosters. Also, the optimizers need to be installed on the host system. But there are new technologies like ffi or wasm available in PHP.

You don't need a plugin to customize a Shopware 6 project

Sun, 04 Jul 2021 23:15:59 +0000

Every developer who has created a plugin has already created a Symfony bundle. All Shopware plugins are extending from a Shopware bundle class which extends from the Symfony bundle. You might now ask yourself: when plugins are bundles, why did you write this blog post? First, let’s list the differences of a plugin and the two types of bundles:

Feature	Plugin	Shopware Bundle	Symfony Bundle
modifying Shopware	✔️	✔️	✔️
can have migrations	✔️	✔️	❌
can be a theme	✔️	✔️	❌
can modify admin / storefront with js/css	✔️	✔️	❌
can be installed, uninstalled (lifecyle)	✔️	❌	❌
can be managed by the shop owner in administration	✔️	❌	❌

The benefits of working with a Bundle

Having less features is sometimes better. As an agency, you don’t want the shop owner to manage your custom built extensions. The lifecycle of plugins is intended mostly for store distribution and often irrelevant in a custom built environment. When you make changes to a project, you want your code to be active always, regardless of the state of the shop. This makes Shopware updates smoother as well, as the upgrade process runs without plugins your code will still run. This solves theme compile issues during update process, e.g. The loading order of the bundles can be fix configured in the config/bundles.php file to fix bundle dependency issues. Also you could store the entire code in the template of the Shopware 6 project.

Setting up a Shopware Environment with Windows

Fri, 16 Oct 2020 00:00:00 +0000

At work I use Linux, but at home I prefer Windows due to gaming. In this short Tutorial I would like to share my Windows setup with you.

My recommended setup includes:

WSL 2
Docker Desktop for Windows
Ubuntu / Debian
GWSL (X-Server for Windows)
PhpStorm
Development Docker setup or my own Docker setup. (We will use my own in this tutorial)

At first we need to install WSL 2 and Docker Desktop. Please follow the tutorials below.

Why I don't like Custom fields?

Tue, 25 Aug 2020 00:00:00 +0000

Normally every project needs custom values saved on products or another entities. Shopware does offer by default Custom fields. It looks nice, but it can produce very fast issues.

Before we start: This is my opinion

Let’s start with a simple Pro Contra list.

Pro

Can be easily created in the Administration / Code.
Can define field types, labels etc and Shopware does the rendering in Administration for me
Loaded by default on the entities
Custom Fields are schema less. You can save anything in it

Contra

Custom Fields are schema less. You can save anything in it
They are saved as JSON
- Hard to modify using SQL
- Cannot have associations
- Slow on SQL Filtering, Aggregation
Loaded by default on the entities
Support between MySQL and MariaDB differs and Performance
Cannot have Flags. All fields are public using Sales-Channel / Store-API
Cause it does not have a Schema they will be indexed as dynamic in Elasticsearch. This brings lot of other problems
You don’t have a control is it translatable or not
Fields values cannot be easy deleted on all entities. You need to modify each entry.

The most problems are introduced cause of the usage of an JSON field. In SQL the accessed fields needs to be extracted. This takes some time of course. On a bigger shop using many products this could leak to performance issues in the listing when it’s used inside a product filter.

How to deploy plugin updates automatically to the Shopware Store

Wed, 18 Sep 2019 00:00:00 +0000

This blog post describes a small example how to automaticly deploy plugin updates to the Store. I will use the FroshPerformance plugin as example.

Preparation

You will need

a Plugin which based on the 5.2 Pluginsystem or Shopware 6 Plugin
a Continuous Integration (i will use Travis as example)
Credentials for the Shopware Account
FroshPluginUploader

Prepare the Plugin itself

You will need a plugin.xml with filled title, version, description, compability and changelog for the languages en and de. All these informations will be picked up automaticly and updated in the Account.

Cluster Setup

Mon, 01 Jan 0001 00:00:00 +0000

This guide assumes you are using Shopware 6.3.0.0 or later

Config Overview

Mon, 01 Jan 0001 00:00:00 +0000

Config Table

config.php Tweaks

Mon, 01 Jan 0001 00:00:00 +0000

Disable Template Cache

Add following code in your config.php to disable the Template Cache

'template' => [
    'forceCompile' => true,
],

Configure SMTP in config.php

'mail' => [
    'type'     => 'smtp', // Possible values: 'mail', 'smtp', 'file'
    'host'     => 'localhost',
    'port'     => 587,
    'ssl'      => 'tls', // Possible values: '', 'tls', 'ssl'
    'auth'     => 'login',  // Possible values: 'plain', 'login', 'crammd5'
    'username' => 'me@localhost',
    'password' => 'mypassword'
],

Redis

When you use Redis for Session and Cache, you must use different databases for each. Otherwise, when you delete your Cache, you will also wipe all your sessions!

DAL exceptions

Mon, 01 Jan 0001 00:00:00 +0000

Expected input to be non empty non associative array.

The entity repositories are built for multiple operations. Example array:

[
  [
    'name' => 'Test'
  ]
]

Recrusion with OneToOne Association

Both sides of the association should not have autoload enabled. Otherwise you have an never-ending recrusion

Event Cheat-Sheet

Mon, 01 Jan 0001 00:00:00 +0000

Shopware_Modules_Order_SendMail_FilterVariables

Manipulate variables of sOrder mail

Shopware_Modules_Admin_CheckUser_Successful

After checked is the user loggedin

Enlight_Controller_Action_MODULE_CONTROLLER_ACTION

Overwrite or add new actions to a controller. In your subscriber you have to return true; at the end

Enlight_Bootstrap_AfterInitResource_DINAME

After a service has been loaded

Enlight_Bootstrap_InitResource_DINAME

Before a service has been loaded or register your own di

Enlight_Components_Mail_Send

Before a mail is sent

Theme_Inheritance_Template_Directories_Collected

An event to register global template directories

Enlight_Controller_Front_DispatchLoopShutdown

It’s the last event before the response is send

Extjs Tweaks

Mon, 01 Jan 0001 00:00:00 +0000

Open backend application with link

With /backend?app=[NAME] can you open any Module (/backend/?app=Article), you can also pass supported variables like /backend/?app=[NAME]&params[NAME]=VALUE (/backend/?app=Article&params[articleId]=1)

Create a real checkbox in config.xml

<element type="boolean">
    <name>test</name>
    <label lang="de">test</label>
    <label lang="en">test</label>
    <options>
      <xtype>checkbox</xtype>
    </options>
</element>

Use components from another backend application

When you want to use components from an another application, you have to load first the App. Otherwise the Ext.Loader cannot find the right controller to load the files.

General exceptions

Mon, 01 Jan 0001 00:00:00 +0000

PageController can’t be requested via XmlHttpRequest

By default Ajax is disabled on all Storefront controllers. You can enable it by adding an new defaults XmlHttpRequest Example:

/**
 * @Route("/widgets/test", name="widgets.test", options={"seo"="false"}, methods={"GET"}, defaults={"XmlHttpRequest"=true})
 */

Introduction

Mon, 01 Jan 0001 00:00:00 +0000

Hey my name is Shyim. In this personal Knowledgebase I will share with you some Tips and Tricks about Shopware.

Introduction

Mon, 01 Jan 0001 00:00:00 +0000

Hey my name is Shyim. In this personal Knowledgebase I will share with you some Tips and Tricks about Shopware.

Plugin System Features with Version

Mon, 01 Jan 0001 00:00:00 +0000

5.2.7

****automatic controller registration

5.2.10

added my_plugin.plugin_dir parameter

5.2.11

config.xml with store values and translateable

5.2.13

5.2.15

cronjob.xml

5.2.17

config type button

Plugins

Mon, 01 Jan 0001 00:00:00 +0000

Add a Smarty Plugin folder with a Plugin

It can be solved with a simple CompilerPass in your Plugin

{% code title=“MyPlugin/Components/CompilerPass/AddTemplatePluginDirCompilerPass.php” %}

<?php

namespace MyPlugin\Components\CompilerPass;

use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
use Symfony\Component\DependencyInjection\ContainerBuilder;

class AddTemplatePluginDirCompilerPass implements CompilerPassInterface
{
    public function process(ContainerBuilder $container)
    {
        $template = $container->getDefinition('template');
        $template->addMethodCall('addPluginsDir', [$container->getParameter('my_plugin.my_parameter_to_folder')]);
    }
}

{% endcode %}

{% code title=“MyPlugin.php” %}

<?php

class MyPlugin extends Plugin
{
    public function build(ContainerBuilder $container)
    {
        parent::build($container);
        $container->addCompilerPass(new AddTemplatePluginDirCompilerPass());
    }
}

{% endcode %}

Inject Plugin Configuration

This method loads only configuration from main shop.

Privacy Policy — Shopware Shop Manager

Mon, 01 Jan 0001 00:00:00 +0000

Last updated: June 12, 2026

Shopware Shop Manager (“the app”) is an Android companion app that lets merchants manage their own Shopware 6 shop. It is operated by Soner Sayakci (s.sayakci@gmail.com).

The short version

The app has no backend, no analytics and no tracking. It communicates exclusively with the Shopware Admin API of the shop(s) you connect. Everything the app stores, it stores on your device.

What the app stores on your device

Shop connection settings: the shop URL, display name, color tag, daily revenue target, low-stock threshold, content language and the access scopes of your login.
Session credential: when you sign in, your admin password is used once to obtain an OAuth session from your shop and is never stored. The app keeps only a revocable, rotating refresh token, encrypted with a hardware-backed key (Android Keystore, AES-GCM). You can revoke it at any time by changing your password or deleting the user session in your shop’s administration.
Shop data cache: a small overview snapshot per shop (revenue figures, order counts, recent orders, low-stock products, pending review count) so the dashboard works offline. It is refreshed from your shop and can be deleted by removing the shop or clearing the app’s data.
Generated documents (PDF invoices/delivery notes) and camera captures are staged in the app’s cache directory only for viewing/sharing/uploading.

Credentials and cached shop data are excluded from Android cloud backup and device-to-device transfer.

Problems and Solutions

Mon, 01 Jan 0001 00:00:00 +0000

Sending a BCC Mail does not work?

Zend-Mailer does not Support BCC on SMTP transport. It drops the Bcc header before sending the mail.

A solution could be to clone the mail and replace the receiver

Plugin-Manager still shows Trial-Version

Open Plugin-Manager and press the Button “Synchronize licenses”. When the button does not exist in your used Version:

Login in your Shopware Account in Plugin Manager
Clear all cookies of the Page
Login in your Backend
Licenses should be now synchronized in Background

Smarty Plugins missing on Finish Page

Can be only fixed with an Update to Shopware 5.4.0

Salary Transparency

Mon, 01 Jan 0001 00:00:00 +0000

I got the idea from Xeiaso to make my salary also transparent.

From Xeiaso:

Please consider publishing your salary data like this as well. By open, voluntary transparency we can help to end stigmas around discussing pay and help ensure that the next generations of people in tech are treated fairly. Stigmas thrive in darkness but die in the light of day. You can help end the stigma by playing your cards out in the open like this.

Smarty

Mon, 01 Jan 0001 00:00:00 +0000

Assign the snippet value to a variable

{s name="NameFromSnippet" assign="tplVariable"}Default Value{/s}
{$tplVariable|replace:'Test':'Lol'}

Read plugin config values

{config name="myVar" namespace="MYPLUGINNAME"}

Check existence of Template file

{if "frontend/foo.tpl"|template_exists}

Supports

Mon, 01 Jan 0001 00:00:00 +0000

Sponsoring possible with:

This awesome people are supporting me:

Github Sponsors

Thanks <3 to Webversiert GmbH for sponsoring me <3
Thanks <3 to Rafael Prukop for sponsoring me <3
Christopher Dosin for sponsoring me <3
Marcus Kreusch for sponsoring me <3
Alexander Wolf for sponsoring me <3

PayPal Supporters

Kai Neuwerth (13,37€)
Sebastian Langer (5€)
Martin Schneider (6,66€)
Uwe Kleinmann (5€)
Joshua Behrens (4,20€)
Michael Telgmann (6,66€)
Christopher Puschmann (5,77€)
Alea123 (6,66€)
Rafael Prukop (25€)
Nils Vosgröne (0,68€)
Lars Schröder (6,66€)
Lars Lohmann (5€)
Sebastian König (5€)
Alexander W.H. Wachert (5€)
Johan Moormann (75€)
David Neustadt (5€)
Christian Voss (50€)
Stefano Rutishauser (15€)

Usefull feature flag overview

Mon, 01 Jan 0001 00:00:00 +0000

Here is an small overview of usefull feature flags:

# Remove cheapest price from normal ProductEntity saves A lot of resources on seo indexer
FEATURE_NEXT_16151=1

# Scopes seo urls to an specific sales channel and only generates seo urls for accessible entities in that sales channel
FEATURE_NEXT_13410=1

# Configure Elasticsearch using default admin search settings (introduced with 6.4.16.0)
FEATURE_NEXT_22900=1

# Basic performance improvments
# only loading required seo associations in DAL
# not calculation empty cards
# checkout/cart returns 204 instead rendering of content
PERFORMANCE_TWEAKS=1