# Docker Compose Published articles for Docker Compose. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Write End-to-End Tests in Your Backend's Language DevFeed: [Write End-to-End Tests in Your Backend's Language]() Original publisher: [Read original article]() Author: James McConkey Published: 2026-09-17T12:00:42Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [Testing](), [Playwright](), [FastAPI](), [Python](), [test data](), [Pydantic](), [SQLAlchemy](), [ASP.NET Core](), [PostgreSQL](), [Docker Compose]() Tags: [asp-net-core](), [code](), [data](), [docker-compose](), [fastapi](), [playwright](), [postgresql](), [project-team-management](), [python](), [sqlalchemy](), [tests](), [the-software-life]() ### AI overview This article argues that end-to-end test-data setup is often the main design challenge, because tests must create consistent domain records while running alongside other tests. It recommends using browser-testing tools in the backend's language when possible, keeping meaningful relationships inline, and extracting small creation helpers without hiding scenario intent. ### Source excerpt The browser is often the easiest part of an end-to-end test. Consider a test that verifies a user can complete an overdue task. The visible interaction is small: sign in, find the task, click Complete, and observe the new status. Before any of that can happen, the test needs a workspace, a user, a project, and [...] The post Write End-to-End Tests in Your Backend's Language appeared first on Atomic Spin. ## New in Symfony 8.2: Console sub-commands DevFeed: [New in Symfony 8.2: Console sub-commands]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-16T07:33:00Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [Command-line interface](), [Code]() Tags: [commands](), [compose](), [console](), [docker-compose](), [git](), [symfony]() ### AI overview Symfony 8.2 adds spaced console sub-commands, allowing command names to form a tree whose levels parse their own options. The update also supports tree-aware help, completion, argument handling, command-chain access, testing, and defining command trees in a single class. ### Source excerpt Symfony console applications group their commands with colon-separated namespaces, such as cache:clear or messenger:consume. Tools like Docker and Git use a different style: spaces separate the levels (docker compose up) and each level parses its own options.... ## Plan Advice in PostgreSQL 19 DevFeed: [Plan Advice in PostgreSQL 19]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-09-15T16:27:53Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [version](), [SQL](), [Docker Compose]() Tags: [analyze](), [beta](), [docker-compose](), [pg-plan-advice](), [postgresql](), [sql]() ### AI overview This tutorial explains PostgreSQL 19's pg_plan_advice and pg_stash_advice modules, which represent query-plan decisions as reusable advice and can apply that advice by query ID. It also describes reconstructing comparable plan advice from ordinary plan output on earlier PostgreSQL versions. ### Source excerpt There is a conversation that happens in every PostgreSQL shop eventually. A query that has been fine for a year gets slow overnight. Nothing was deployed. The data grew a little, ANALYZE ran, and the planner -- entirely reasonably, on the numbers it had -- picked a different plan. The old plan was better. You would like it back. PostgreSQL 19 ships two new modules for exactly this: pg_plan_advice, which can read a plan back out as a string and enforce it later, and pg_stash_advice, which keeps those strings keyed by query id and applies them automatically. ▸ Every query below ran against the Lab, the free dataset bundle used throughout this blog, on PostgreSQL 19 Beta 3: POSTGRES_VERSION=19beta3 PG_MAJOR=19 docker compose up. Both modules are contrib, and the Lab image ships them; nothing below runs a LOAD to enable them, because the server already has them -- pg_plan_advice in session_preload_libraries, pg_stash_advice in shared_preload_libraries (it can survive a restart, which needs loading that way). One line each in postgresql.conf, or the equivalent server-start flag, and you're done. pg_stash_advice still needs its own CREATE EXTENSION, further down, for its SQL functions -- that's independent of how the module itself got loaded. ## Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts DevFeed: [Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-12T12:32:29Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Docker](), [Docker Compose](), [Homelab](), [Open Source](), [GitOps]() Tags: [containers](), [docker](), [docker-compose](), [gitops](), [home-lab](), [home-server](), [open-source]() ### AI overview The article explains how Komodo, an open source platform, can centrally manage Docker servers, containers, Compose stacks, and deployments across multiple hosts, reducing the need to update each stack manually. ### Source excerpt There are SO many tools out there that allow you to keep your containers updated and I have used just about all of them, including Watchtower, Dockcheck, and others. Running... The post I Stopped Manually Updating My Docker Container Stacks. I Use This Instead appeared first on Virtualization Howto. ## If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things DevFeed: [If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-11T12:53:06Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Proxmox](), [backups](), [Docker](), [Docker Compose]() Tags: [backups](), [docker](), [docker-compose](), [home-lab](), [home-server](), [proxmox](), [virtualization]() ### AI overview A practical two-hour home lab maintenance plan covering selective updates, backup verification, storage health, reboot checks, and focused remediation. It discusses Proxmox hosts, Docker images, Docker Compose stacks, and optional automatic updates. ### Source excerpt Let's face it, our time in the home lab among other things we have going on in our lives and families may be hard to come by and there are... The post If I Had 2 Hours for My Home Lab This Weekend, I'd Do These 7 Things appeared first on Virtualization Howto. ## Getting Ready for PostgreSQL 19 DevFeed: [Getting Ready for PostgreSQL 19]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-09-03T13:09:30Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [upgrade](), [Release notes](), [SQL](), [Docker Compose](), [Docker](), [Linux]() Tags: [beta](), [compatibility](), [docker](), [docker-compose](), [linux](), [postgresql](), [release-notes](), [sql](), [upgrade](), [version]() ### AI overview This article reviews PostgreSQL 19 Beta 3 ahead of its general availability, focusing on upgrade-relevant compatibility changes and useful SQL additions. It highlights changes involving JIT defaults, authentication, GiST indexing, naming restrictions, and configuration capacity, and includes queries tested against a PostgreSQL 19 Beta 3 instance. ### Source excerpt PostgreSQL 19 Beta 3 shipped on August 13, 2026, and the release notes have been filled in as of 2026-07-18 -- still marked subject to change, and the GA date isn't announced yet, but following the project's usual September/October cadence general availability should land within the next few weeks. That makes now the right time to read through what's changing, the same way I did for PostgreSQL 11 through 18 a few weeks ago. This is not a changelog dump. It's the subset of PG 19 I think is worth knowing about before you upgrade: a handful of compatibility breaks that will bite people who don't read release notes, and the SQL-level additions I found genuinely useful once I started poking at them. Every query below ran against a real PostgreSQL 19 Beta 3 instance -- no hand-waving about syntax that might work. ▸ Every query in this article ran against the Lab, the same free dataset bundle used in the rest of this blog (F1 data, geopolitical data, music data, and more), pinned to a real PostgreSQL 19 Beta 3 instance. PG 19 support isn't the Lab's default yet, but there is a prebuilt beta image on the registry, for both linux/amd64 and linux/arm64 -- so POSTGRES_VERSION=19beta3 PG_MAJOR=19 docker compose up pulls it rather than building anything, and every query below reproduces on it exactly as printed. (PG_MAJOR only matters if Compose ends up building; it costs nothing to set.) Plain docker compose up still pulls the PG 16 image, and stays the default until 19 reaches general availability. ## Upgrading Rails 4.2 to Rails 8: Count Sites, Not Warnings DevFeed: [Upgrading Rails 4.2 to Rails 8: Count Sites, Not Warnings]() Original publisher: [Read original article]() Published: 2026-08-08T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Rails](), [upgrade](), [version](), [Test coverage](), [RSpec](), [Docker Compose](), [Ruby]() Tags: [coverage](), [docker-compose](), [rails](), [rspec](), [ruby](), [upgrade](), [version]() ### AI overview An account of upgrading a multi-tenant JSON API from Rails 4.2.7.1 to Rails 8. The author argues that estimates focused on version gates missed the actual risks, and describes how characterization tests, an extracted frontend, and containerized development reduced the work. ### Source excerpt . [Upgrading Rails 4... ## Immich: tu galería de fotos autoalojada DevFeed: [Immich: tu galería de fotos autoalojada]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-06T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker Compose](), [Homelab](), [Nextcloud](), [Open Source]() Tags: [docker-compose](), [homelab](), [open-source]() ### AI overview This Spanish tutorial presents Immich as a self-hosted, open-source photo and video platform that runs on a personal server. It compares Immich with Nextcloud, explains local facial recognition and semantic search, and outlines hardware, architecture, filesystem, storage, and Docker Engine requirements. ### Source excerpt Instala Immich con Docker Compose: galería tipo Google Fotos con reconocimiento facial y búsqueda por IA que corren en tu propio servidor. ## Vaultwarden: gestor de contraseñas autoalojado DevFeed: [Vaultwarden: gestor de contraseñas autoalojado]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker](), [Docker Compose](), [TLS (Transport Layer Security)](), [nginx](), [proxy](), [backups]() Tags: [backups](), [bitwarden](), [compose](), [docker](), [docker-compose](), [hardening](), [homelab](), [https](), [nginx](), [proxy](), [tls](), [vaultwarden]() ### AI overview A Spanish-language tutorial explains how to self-host Vaultwarden, an unofficial Rust server compatible with Bitwarden clients. It covers Docker Compose deployment, HTTPS behind an Nginx reverse proxy, admin-token hardening, and backups, while noting the trade-off between community support and the official Bitwarden server. ### Source excerpt Instala Vaultwarden con Docker: servidor ligero compatible con los clientes de Bitwarden, con HTTPS, hardening del admin token y backups. ## Traefik: proxy inverso para contenedores DevFeed: [Traefik: proxy inverso para contenedores]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [traefik](), [Docker](), [proxy](), [let's encrypt](), [Docker Compose](), [TLS (Transport Layer Security)]() Tags: [docker](), [docker-compose](), [let-s-encrypt](), [proxy](), [tls](), [traefik]() ### AI overview This tutorial explains how Traefik acts as a reverse proxy for Docker containers. It covers automatic container discovery through Docker labels, routing with entryPoints, routers, and services, and automatic HTTPS certificates through Let's Encrypt. It also compares Traefik with manually configured Nginx and mentions Caddy as an alternative. ### Source excerpt Traefik detecta tus contenedores Docker automáticamente y les da HTTPS con Let's Encrypt vía labels, sin tocar un fichero de configuración. ## Docker: guía práctica de contenedores en Linux DevFeed: [Docker: guía práctica de contenedores en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-02T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker](), [Linux](), [Docker Compose](), [Dockerfile](), [container](), [Command-line interface](), [Kernel]() Tags: [cgroups](), [cli](), [compose](), [container](), [debian](), [distro](), [docker](), [docker-compose](), [dockerignore-usage](), [kernel](), [linux](), [oci](), [podman](), [python]() ### AI overview A practical Spanish-language guide to Docker on Linux. It explains container isolation through Linux namespaces and cgroups, installation on Ubuntu/Debian, Docker architecture, image layers and Dockerfiles, and introduces networks, volumes, Docker Compose, and security practices. ### Source excerpt Guía práctica de Docker: arquitectura, capas de imagen, redes, volúmenes, Docker Compose y buenas prácticas de seguridad, con ejemplos reales. ## SQL Improvements in PostgreSQL 11-18: A Personal Selection DevFeed: [SQL Improvements in PostgreSQL 11-18: A Personal Selection]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-07-28T14:39:25Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [SQL](), [version](), [Docker Compose](), [datasets]() Tags: [docker-compose](), [improvements](), [personal](), [postgresql](), [sql](), [version]() ### AI overview A personal, theme-based selection of SQL improvements introduced across PostgreSQL versions 11 through 18. The article relates these features to query writing and briefly discusses broader release categories and contributor priorities. ### Source excerpt Seven major versions of PostgreSQL shipped between 2018 and 2025, one per year without exception, and each with a changelog of 150 to 200 user-visible changes. Each release covers a broad canvas -- performance, replication, administration, and security -- but every one of them also advanced the SQL layer, filling gaps in the standard, adding missing functionality, or cleaning up long-standing rough edges. Working through the new edition of The Art of PostgreSQL forced me to catalogue them all; this is my selection of the features I kept reaching for while rewriting the examples. I hope it's useful beyond that context -- organized by theme, with the version each feature landed in. ▸ All queries in this article run against the Lab, a free dataset bundle that includes the F1 database, geopolitical data, music data, and more -- so you can try every example yourself. The Lab is a docker compose up away: it starts PostgreSQL with all datasets loaded and a query UI web app that runs in your browser, with EXPLAIN plan diagrams, and SVG rendering for PostGIS results on geo queries. To get a sense of where the community actually puts its effort, Noriyoshi Shinoda of Hewlett-Packard Enterprise Japan has been publishing a meticulous "PostgreSQL New Features with Examples" series for every major release since version 9.4 -- each edition catalogues every user-visible change with a working code example. Counting his categories across PG 11-18 gives a clear picture of contributor priorities: Release SQL Performance Admin & Ops Replication Security Other PG 11 5 6 5 3 4 3 PG 12 4 6 7 3 3 5 PG 13 7 8 10 6 5 6 PG 14 4 7 6 5 3 5 PG 15 2 5 6 5 3 8 PG 16 4 6 8 5 7 8 PG 17 5 7 8 8 4 6 PG 18 4 3 4 3 2 5 Sum 35 48 54 38 31 46 New features by category per release (Shinoda count) SQL is the smallest category. Admin & Ops leads across the whole period, followed by Performance -- which reflects who funds the project: Amazon (Aurora), Google (AlloyDB), and Microsoft (Azure) all have strong commercial ## Diagnosing a 28,232-Connection SSE Limit in a Go Leaderboard DevFeed: [Diagnosing a 28,232-Connection SSE Limit in a Go Leaderboard]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2026-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Server-sent events (SSE)](), [Go Language](), [Docker Compose](), [Redis](), [Grafana](), [Prometheus]() Tags: [docker-compose](), [go](), [grafana](), [prometheus](), [redis](), [sse]() ### AI overview A tutorial on testing and diagnosing the SSE connection limit of a Go leaderboard service. It describes the service architecture, Docker Compose deployment, and monitoring with Prometheus and Grafana. ### Source excerpt Why my Go leaderboard's capped at exactly 28,232 SSE connections, how Docker networking got me to 150k, and the path toward millions. ## Workload Capture & Replay DevFeed: [Workload Capture & Replay]() Original publisher: [Read original article]() Published: 2026-02-09T23:00:00Z Content type: article Language: en Sources: [Dennis Felsing]() Topics: [Tooling](), [Docker Compose](), [synthetic-data]() Tags: [blog-post](), [docker-compose](), [regression](), [state](), [synthetic]() ### AI overview This article introduces workload capture and replay tooling for reproducing production issues. It records a Materialize instance's state, recent queries, and ingestion rates, then replays them in a Docker Compose environment using synthetic data. ### Source excerpt When customers hit issues in production, it can be an effort to locally reproduce them, especially when external sources are involved. Reproducing issues is useful not just to figure out the root cause, but also to verify the fix and add a regression test. The newly introduced workload capture & replay tooling records a Materialize instance's state as well as recent queries and ingestion rates, then replays them in a Docker Compose environment with synthetic data. In this blog post I'll show how it works and talk about some of the challenges and future work. Read the rest of the blog post over on the Materialize blog. ## Running our Docker registry on-prem with Harbor DevFeed: [Running our Docker registry on-prem with Harbor]() Original publisher: [Read original article]() Author: Farah Schüller Published: 2025-08-24T17:00:00Z Content type: tutorial Language: en Sources: [37signals Dev]() Topics: [docker registry](), [on-prem](), [Docker](), [Docker Compose](), [Deployment]() Tags: [deployment](), [docker](), [docker-compose](), [docker-registry](), [harbor](), [on-prem](), [open-source](), [registry]() ### AI overview The article describes 37signals' move from external container registries, including Docker Hub and Amazon Elastic Container Registry, to an on-premises Harbor registry. It explains cost, performance, security, governance, and independence concerns, then outlines a single-server Docker Compose deployment using the organization's own S3 storage and plans for replicated sites. ### Source excerpt On hosting images without the price tag. ## Hosting Bugsink on Coolify DevFeed: [Hosting Bugsink on Coolify]() Original publisher: [Read original article]() Author: Julien Published: 2025-07-07T20:33:23Z Content type: tutorial Language: en Sources: [Thoughts, stories and ideas.]() Topics: [Docker Compose](), [Deployment](), [Docker](), [Cross-origin resource sharing (CORS)]() Tags: [bugsink](), [coolify](), [deployment](), [docker](), [docker-compose](), [environment-variables](), [http](), [https](), [redirection](), [testing]() ### AI overview This tutorial explains how to deploy Bugsink on Coolify with Docker Compose while a Coolify bug prevents the default Bugsink deployment template from working correctly. It covers port redirection, HTTPS, domain configuration, and environment variables. ### Source excerpt A simple Docker Compose setup to host Bugsink using Coolify that supports HTTPS ## Testing Tracing Locally with OpenTelemetry (OTel) DevFeed: [Testing Tracing Locally with OpenTelemetry (OTel)]() Original publisher: [Read original article]() Author: Christian Campos Published: 2025-06-26T13:03:08Z Content type: tutorial Language: en Sources: [Apartment 304]() Topics: [tracing](), [OpenTelemetry](), [Testing](), [Docker Compose](), [Docker](), [Go]() Tags: [apartment-304](), [custom-software-solutions](), [devops](), [devops-engineer](), [docker](), [docker-compose](), [go](), [instrumentation](), [opentelemetry](), [software-architecture](), [software-development](), [software-engineer](), [testing](), [tracing]() ### AI overview This tutorial explains how to test distributed tracing locally with the OpenTelemetry Collector, Docker Compose, and a minimal Go application. It describes how local tracing avoids development friction from API keys, rate limits, network delays, and cloud-service costs. ### Source excerpt A quick and easy way to visualize how your programs and services connect and perform. ## Windmill for AI Workflows - Investing.com Case Study DevFeed: [Windmill for AI Workflows - Investing.com Case Study]() Original publisher: [Read original article]() Author: Yonathan Adest Published: 2025-02-24T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [Automation](), [data-processing](), [Artificial Intelligence](), [etl](), [tracing](), [Logging](), [PostgreSQL](), [airflow]() Tags: [ai](), [airflow](), [automation](), [case-study](), [case-study-testimonial-fintech-investing](), [data-processing](), [docker-compose](), [embeddings](), [etl](), [fintech](), [human-review](), [investing](), [pdf](), [postgresql](), [push-notifications](), [recommendations](), [testimonial](), [windmill](), [workflows]() ### AI overview This Investing.com case study describes how its AI team uses Windmill to orchestrate content processing and distribution, stock-analysis report generation, and ETL workflows. The workflows use webhooks, AI models, vector embeddings, human review, and PostgreSQL, while Windmill provides tracing, logging, and Docker Compose deployment. ### Source excerpt This is a testimonial from Yonathan Adest, CTO at Investing.com, about how Windmill has helped them to automate their workflows and improve their data processing capabilities. ## The CI Flake DevFeed: [The CI Flake]() Original publisher: [Read original article]() Published: 2024-08-15T22:00:00Z Content type: article Language: en Sources: [Dennis Felsing]() Topics: [ci](), [Docker Compose](), [debug](), [Python]() Tags: [bugs](), [ci](), [continuous-integration](), [debug](), [docker](), [docker-compose](), [integration](), [python]() ### AI overview The article investigates a rare flaky test failure in Materialize CI that became more frequent after tests moved from AWS to Hetzner Cloud. It documents attempts to diagnose the issue, including flushing a generated docker-compose.yaml file, reproducing the failure, and examining parallel execution and CI setup. ### Source excerpt I analyzed a flaky test failure in our Materialize CI today: $ docker compose up -d --scale default=0 default no such service: default mzcompose: error: running docker compose failed (exit status 1) I had seen this error already once or twice in the last year, but it was incredibly rare in our Continuous Integration (CI) runs, and never happened locally. As usual, there were more pressing product issues to debug, so I never looked into it. But last week I switched most of our CI tests to run on Hetzner Cloud instead of AWS to save some money. Suddenly this issue started occurring more often in CI, so my thinking was that it must somehow be timing-dependent. Before investigating my first instinct was that we are not writing the docker-compose.yaml file properly, which had already led to flaky calls to Docker Compose before (source code): file = self.files.get(thread_id) if not file: file = TemporaryFile(mode="w") os.set_inheritable(file.fileno(), True) yaml.dump(self.compose, file) self.files[thread_id] = file So yesterday I added a file.flush() after the yaml.dump and hoped to be done with it. This morning I woke up and the issue was still occurring! Based on the logged docker call this should be the code causing the problem (source code): def handle_composition( self, args: argparse.Namespace, composition: Composition ) -> None: if args.workflow not in composition.workflows: # Restart any dependencies whose definitions have changed. # This is Docker Compose's default behavior for `up`, but # not for `run`, which is a constant irritation that we # paper over here. The trick, taken from Buildkite's # Docker Compose plugin, is to run an `up` command that # requests zero instances of the requested service. if args.workflow: composition.invoke( "up", "-d", "--scale", f"{args.workflow}=0", args.workflow, ) super().handle_composition(args, composition) else: [...] Running the test in an endless loop locally had no success of reproducing the issue: while true; do bin/mzcom ## May the LLM be with You - On Planes and German Trains DevFeed: [May the LLM be with You - On Planes and German Trains]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-12-30T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [LLMs](), [devex](), [Development](), [Refactoring](), [Back end](), [Docker Compose](), [nginx](), [Kubernetes]() Tags: [ai-for-devex-artificial-intelligence-developer-experience-developer-productivity-software-develo](), [backend](), [devex](), [docker-compose](), [grpc](), [kubernetes](), [llm](), [nginx](), [refactoring](), [software-development]() ### AI overview This personal developer account explores using local LLMs for software development when internet access is unavailable or data-privacy concerns prevent using cloud tools. It describes refactoring backend services and replacing an unused gateway in a Docker Compose setup while traveling offline. ### Source excerpt May the LLM be with You - On Planes and German Trains This might be the unofficial seventh part of the "AI for DevEx" series. LLM tools are a great help during the entire software development process. But what if we are offline or if data privacy concerns disallow using ChatGPT and similar tools? ## The foundation of the new Temporal CLI experience DevFeed: [The foundation of the new Temporal CLI experience]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2023-03-30T04:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [cross-platform](), [Docker Compose](), [Docker](), [Development](), [Node.js]() Tags: [cross-platform](), [development](), [docker](), [docker-compose](), [node-js](), [temporal-concepts]() ### AI overview The article describes the three-year effort behind a single-binary, cross-platform Temporal development experience. It explains that Docker Compose was previously the official local-development approach, while Docker added overhead for some developers, and outlines the Temporal Cluster components involved, including services, a UI server, and required persistence and visibility dependencies. ### Source excerpt Back when I joined Temporal in early 2020, one of the first things our CEO and co-founder Maxim said to me was, "we need a single binary." ## An Annotated Docker Config for Frontend Web Development DevFeed: [An Annotated Docker Config for Frontend Web Development]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-03-22T16:12:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Web Development](), [DevOps](), [Development](), [Docker Compose](), [Dockerfile]() Tags: [allows](), [apple-silicon](), [config](), [development](), [devops](), [docker](), [docker-compose](), [environment](), [frictionless](), [frontend](), [insights](), [local](), [making](), [multi-arch](), [needs](), [onboarding](), [project](), [shrink-wrap](), [web-development]() ### AI overview This tutorial explains how to use Docker as a local development environment for frontend web projects. It presents a reusable configuration approach that packages each application with the environment and service versions it needs, making environments reproducible, disposable, and easier to share. Examples reference Craft CMS, Laravel, NodeJS, and Rails, with multi-architecture base images available for Apple Silicon. ### Source excerpt A local development environment with Docker allows you to shrink-wrap the devops your project needs as config, making onboarding frictionless ## Use replica database for read-only transactions DevFeed: [Use replica database for read-only transactions]() Original publisher: [Read original article]() Published: 2019-11-27T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Transactions](), [Spring Boot](), [MariaDB](), [Replication](), [Docker Compose](), [Amazon Web Services]() Tags: [aws](), [docker-compose](), [mariadb](), [replication](), [spring-boot](), [transactions]() ### AI overview This tutorial shows how to configure a Spring Boot application to route read-only transactions to a replica database while continuing to write data to the master. It describes a setup using MariaDB instances, replication, Docker Compose, and AWS RDS, while noting that the example replication configuration is intended for testing rather than production. ### Source excerpt Some time ago we had a problem with performance caused by generating big reports for users. During one of the firehouse meetings, there was an idea to generate reports from the replica database. We've solved the issue differently but the idea got me interested. In this post, I'll configure spring-boot based application to use the replica database for all read-only transactions. Read more ## Building a Home Media Server with Docker Compose DevFeed: [Building a Home Media Server with Docker Compose]() Original publisher: [Read original article]() Published: 2019-07-03T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Docker Compose](), [Docker](), [Linux](), [Server]() Tags: [docker](), [docker-compose](), [linux](), [server](), [setup]() ### AI overview A practical guide to repurposing an Intel NUC as a headless home media server. It covers hardware choices, Ubuntu installation, Docker and Docker Compose setup, storage mounting, and permissions, with plans for streaming content and sharing files across a home network. ### Source excerpt I recently moved into a bigger condo which had a wall mount pre-installed in the bedroom for a TV, so I decided to take advantage of it and bought a second TV. Previously, I was using an Intel NUC attached to my TV and running LibreElec. If you've not heard of LibreElec, it's a very cool minimal Linux OS that sets itself up to run Kodi. It is remarkably easy to set up, and even found and setup my obscure USB remote control automatically. [Next page]()