Traefik Error Page
The default Traefik error page is not great, but it can be improved with these steps.
Development tools, Continuous Integration and Continuous Delivery/Deployment (CI/CD), and generally the processes that streamline development operations.
The default Traefik error page is not great, but it can be improved with these steps.
Here's how I set up a Google Gem prompt to give me better results for Drupal help.
If you're managing several sites with developer environments, traefik can make your local experience better.
Drupal offers a few types of phpunit regression testing suites, and those tests can also be run in CI/CD and in local development.
GitLab is the most powerful and user-friendly. GitHub is the most ubiquitous. Codeberg is the most ethical. Worktree is the most (only) Canadian.
I developed a semi-automated method to keep databases roughly in sync across environments.
Pa11y and Pa11y-ci are helpful accessibility testing tools, as part of your CI workflow or running locally.
Playwright is a helpful testing tool, both locally and in your CI processes.
PHP Linting and CS Testing in VS Code and as CI/CD jobs can help reinforced Drupal best practices.
Using GitLab CI/CD to deploy new containers with Docker swarm, and run the Drupal database update script.