Petter

Optimized configuration for Thirtybees on Orangepi 5 , using Brotli compression: orangepi5config Nginx configuration and documentation for thirty bees e-commerce store on Orange Pi 5. Testing done with 500 test products in database. Hardware Component Specification Machine Orange Pi 5 RAM 8GB Storage NVMe OS Armbian 26.2.0 Bookworm (Debian 12, aarch64) Stack Component Version / Details Nginx 1,31.2 (recompiled with ngx_brotli) PHP 8.3-FPM, 24 workers Database MariaDB, 256MB indob_buffer_pool Cache fastcgi_cache (1GB RAM) + Valkey/Redis Compression Brotli + Gzip Opcache 256MB HTTP/3 Ready in binary, activated in production Performance Apache Benchmark — ab -n 10000 -c 100 -k Configuration Req/sec Latency Failed Baseline (no cache) 271 176ms 0 fastcgi_cache 8 025 12.5ms 0 fastcgi_cache + Brotli 9 630 10.4ms 0 Optimized for 8GB 10 593 9.4ms 0

orangepi5-thirtybees-setup.md orangepi5-thirtybees-setup.md

ab -n 10000 -c 100 -k https/XXXX.XX/index.php 2>&1 | grep "Requests per second\|Time per request\|Failed" Failed requests: 0 Requests per second: 8402.12 [#/sec] (mean) Time per request: 11.902 [ms] (mean) Time per request: 0.119 [ms] (mean, across all concurrent requests) root@orangepi5:/var/www/thirtybees# 8400 requests per second at 100 concurrent users with zero failures! That's an absolutely remarkable result for an ~$80 ARM board. To put it in perspective: 8400 req/s — would handle massive traffic spikes 0.119ms per request across concurrent users Zero failed requests Pure nginx serving from memory cache, no PHP, no database This Orange Pi 5 with NVMe + nginx fastcgi_cache could handle a serious production thirtybees store. Most small/medium e-commerce sites see maybe 10-50 req/s peak traffic. Final stack summary: ✅ Nginx 1.29 with fastcgi_cache ✅ PHP 8.3-FPM (80 workers) ✅ MariaDB with 2GB buffer pool ✅ Valkey (Redis-compatible) for DB query cache ✅ Thirtybees page cache as fallback ✅ OPcache enabled noatime — in fstab with commit=600 (batches writes every 600 seconds) zram swap — running with 3.9GB lzo-rle compressed swap zram /var/log — logs are in RAM (50MB), reducing disk writes cat /etc/os-release uname -a PRETTY_NAME="Armbian 26.2.0-trunk.811 bookworm" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.armbian.com/" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 26.2.0-trunk.811 bookworm" Linux orangepi5 6.1.115-vendor-rk35xx #1 SMP Sat Apr 25 16:15:42 UTC 2026 aarch64 GNU/Linux root@orangepi5:/var/www/thirtybees#

Hi! Are there any experienced Thiry bees developers here who can undertake paid work with upgrading to Thirybees from Prestasop 1.6.24?

Quite good results using pagespeed insights for checking this site https://pagespeed.web.dev/analysis/https-www-promopro-se-101793-elektronik-mobil/ubrwmy844p?form_factor=mobile

I'm using Nginx and Nginx do not use .htaccess file. Can't the same be done using fail2ban ?

mod_xx mostly refers Apache. I normally use Nginx and have very good experience using https, brotli and pagespeed so my recommendation will be to combine these three. I think brotli will do the compression for you so you don't need mod_deflate,,,, but I might be wrong. mod_http2 mod_brotli mod_pagespeed

Can Google Ads webhook integration be done with Thirtybees ? Google: Set up a webhook integration for a lead form extension

When testing a default installation of Thirty Bees, using Google Chrome Lighthouse, there are 9 warnings regarding Trust and safety: [email protected] - 5 medium Vulnerabilities [email protected] - 4 medium Vulnerabilities. Please see attached screenshot. Any recomandations ?

What about hosing your own small server ?? - If you have access to a fiber internet access, you can also be your own hosting provider. Let a hosting provider handle your email (to complicated for to do your self safely without some experience and knowledge) and get your registrar to forward the domain to the IP of the fiber line. Any hardware built in the last 10 years will be sufficient to host a "pretty low volume site", if running Debian/ Ubuntu Linux or similar. Even the new Raspberry Pi 4 with 4 or 8 gb memory are quite capable to host a small site if equipped with a SSD like the Samsung T5. And believe me: If a solution like the raspberrypi4 suggested above is not sufficient, or you fear poor performance, you have a luxury problem, since the raspberry4 8 GB version with SSD is a quite capable small solution for hosting a thirty bees website.

When testing a default install of Thirtybees 1,3 (updated with core updater), using Chrome Lighthouse, I get 1 warning about insecure request and also that 9 vulnerabilities is detected, namely [email protected] and [email protected] the site is correctly configured for https and http2, using Let's Encrypt and is redirecting all traffic to https, nut still somwhere a http link is trying to load ,,,, See attached image.

Many thanks, I commented out line 117 in /modules/productcontact/views/css/jquery.fbox.css, and now it is working as intended. The problem seems to have been introduced by the produccontact module from FME modules.

I have a "test" site up, running a default install of Thirtybees 1.3.0-main updated to bleeding edge with core updater. When looking at product images, the image is "cut" on the left and right side, leaving only the middle of the image fully visible. See link: http://valifest.com/en/coffee-and-tea/tea/tea-cans The site is running on a Raspberrypi4 - Ubuntu server 64 bit and nginx version: nginx/1.19.10 - PHP7.4 any one out there have a clue about what's wrong ?

It is not everyday you see someone that seems to understand these key factors that Jollyfrog pinpoints. For all of you interested in getting good ranking, take note of these very important advices and implement all of them before trying other measures.

I'v just tried your link, using Vivald, Firefox and Chrome browser - can confirm that the product pic on the product page does not work in any of these browsers.