TRAEFIK CONFIGURATION FOR DOCKER COMPOSE SETUPS
Recently I played around with letting multiple smaller applications run, containerized, and published via Traefik as the central Gateway and SSL handler. Initial setup was simple - but adding more applications and separating the applications and their backend services into separate docker networks caused problems. The problem I ran into an error that was initially hard to get a grip on, because it was sometimes there, sometimes not a restart via docker-compose up changed the situation all the time (even without changes to the docker-compose.
A MISLEADING ERROR MESSAGE IN DB MIGRATIONS
A few days ago we ran into the following error messages during deployment of a Flow 7.x based application where the deployment failed while executing the database migrations:
An exception occurred while executing 'ALTER TABLE vendor_package_domain_model_something ADD CONSTRAINT FK_BD82590B2B219D70 FOREIGN KEY (entry) REFERENCES vendor_package_domain_model_something_else (persistence_object_identifier)': SQLSTATE[HY000]: General error: 1005 Can't create table package. vendor_package_domain_model_something (errno: 150 "Foreign key constraint is incorrectly formed") It took a while to understand that the migration itself was not the problem and fully OK.
MIGRATING FROM KIRBY TO HUGO
Despite working with the PHP based content management systems TYPO3 and Neos on a daily base for over 15 years, about 10 years ago when I last “relaunched” my personal website, I decided to use a different approach. Back then I decided to use Kirby that has evolved a lot since then. I never really upgraded Kirby and rarely wrote any blog posts anyway. Fast forward to end of 2022 I wanted to do some more with my website again and looked into a new static site generator so I can build the site locally or in a Gitlab CI build pipeline and just publish the resulting static files from there on.
HOW TO LIST ALL .CH DOMAIN NAMES
Intro Starting from January 1st 2021, SWITCH started to publish the .ch zone with all *.ch domain names as one of a few TLD operators. With this, each and everyone can have a look into all avilable and active domain names within the .ch zone that have a DNS delegation set. Details and limitations are listed on the open data page at SWITCH. Fetch the whole .ch zonefile I followed the example command that Markus Ritzmann tweeted:
SETTING UP DDEV FOR FLOW BASED PROJECTS
Intro Since years, this is one of the topics that comes back every now and then - and until now it was always a choice out of many ways that all had their good sides but also their drawbacks. Until now, I used several things to develop PHP based projects: local on Mac, with MAMP local on Mac, within a Vagrant-Box local on Mac, with Homebrew-based installations of Nginx, PHP-FPM and MySQL on a shared Development-Server But now I learned about ddev and how it solves many of the issues the above solutions had.
BUILDING LOMSY WITH FLOW, PART 3
Get agile, deploy early! This episode will guide you through setting up Gitlab CI deployment for the Flow application. Add vHost on target machine To be able to deploy the application to some server, it’s usually needed to prepare a virtual host or vHost on that target machine - unless you order a server for your application alone. So far, I more often saw myself deploying to a shared server, where each application resided inside it’s own vHost.
BUILDING LOMSY WITH FLOW, PART 2
Fasten your seat-belts - launching Flow in progress! This episode covers the basic setup of a Flow based application including gulp.js frontend workflow. If you follow along, you’ll have a working frontend-workflow with SASS compilation, CSS minifying, and an first view of your application that you can access via your Browser. I hope you enjoy this story or tutorial (I’m still unsure how to call it) - please let me know whether you miss something or liked it, I’m happy to hear from you.
BUILDING LOMSY WITH FLOW, PART 1
This is the first part of a series of posts. Instead of writing a “boring” tutorial with a fictional project, I decided to write down some steps on the journey of actually building a little side-project. I hope you can use my explanation for something and would be very happy to hear from you - both if you liked it, or if you spotted a mistake or have a comment to improve.
WAYS TO ADD CACHE-BREAKING FOR STATIC ASSETS IN TYPO3 NEOS
Updated 2015-04-01, added solutions E, F and G Updated 2017-02-22, updated solution D The problem Given you work on a project and continuously deploy new versions of the site, you’ll probably also deliver fresh static assets like CSS and JS files. We noticed that our changes (including bugfixes) were not recognized by the browser of the user/customer… The reason was mostly, that the CSS/JS files were cached locally by the browser from an earlier visit.
ADDING A LIGHTBOX EFFECT TO YOUR CONTENT IN TYPO3 NEOS
The problem Neos was designed to provide a small but stable base for content management needs. This implies, that certain functionality or features are not provided by the creators of Neos upfront - but can be implemented as needed by everyone that needs it. For us, this meant that the well known “enable click-enlarge” checkbox from TYPO3 CMS just doesn’t exist in Neos - and also no lightbox effect is implemented on content images right away.