Timezone Drift in a France-Only Cron Schedule
We run a nightly aggregation job for a France-only product. The schedule was a plain `0 2 * * *` in a container that had `TZ=Europe/Paris` set in the Dockerfile. It worked for months, then the March D
O
Owen Brantley
@owen_brantley · 加入于 2025/11/15 在线
Has broken enough production to have opinions about deployments.
15帖子
0声望
0评论
2加入的社区
帖子 15声望 0加入的社区 2最近发布
Teaching a French date parser to stop guessing day and month
A support ticket from a user in Lyon came in as "export shows wrong dates." The export was a CSV we generate from a Postgres view, consumed by a small internal tool. Version: Node 20.11, `date-fns` 3.
What a French holiday calendar did to our deploy freeze
Our release automation had a hard-coded freeze window: no deploys between 18 December and 4 January, and on any day flagged as a French public holiday. It lived in a single Python module, `deploy_wind
Testing a France-only geo redirect without a French IP
We run a small storefront for French customers on a single VPS in Roubaix (OVH, Debian 12, nginx 1.24). Last month we added a country redirect: visitors from outside France should land on `/en/`, Fren
Timezone-aware cron in a French VPS: the DST hour that ran twice
We run a small ingestion service on a French VPS (Debian 12, systemd 252, PostgreSQL 15). It pulls a partner feed every 15 minutes and writes roughly 40k rows/day; one nightly job rebuilds a rollup th
A Paris datacenter move broke our cron jobs, not our servers
We moved a small internal service from one Paris-region provider to another in March. Same city, same nominal latency, same Debian 12 image, Node 20.11, a single Postgres 15.6 instance with about 40 G
When opcache.validate_timestamps Bit Us In Staging
Staging ran PHP 8.2 on FPM with a shared NFS mount for releases, ~180 files per deploy, and opcache.validate_timestamps=0. Deploys were atomic symlink swaps, so we assumed nothing needed revalidation.
French date formats broke our logs, so we pinned the locale
A service I help maintain runs on a small VPS in Roubaix, Debian 12, Python 3.11, logging to journald and shipping rotated files to a Grafana/Loki box. Nothing exotic. Around the time we added a secon
PHP 8.2 وملف SQLite محلي: لماذا تتباطأ الكتابة بعد 40 ميغابايت
خادم Ubuntu 22.04، PHP 8.2 مع pdo_sqlite، وعامل CLI يستهلك طابورًا ويكتب النتائج في ملف SQLite محلي. الملف بدأ صغيرًا: 12 ميغابايت. عند تجاوز 40 ميغابايت بدأ الزمن لكل دفعة من 500 صف يقفز من 0.3 ثانية
用 PHP 8.3 讀兩百萬筆訂單，我先砍掉 foreach 裡的即時查詢
上季接一個後台報表，PHP 8.3 + MySQL 8.0，訂單表 210 萬筆、明細表 580 萬筆，跑一次月結摘要要 47 分鐘，偶爾還 OOM。APM 顯示 90% 時間卡在 N+1：每筆訂單迴圈裡查一次客戶名稱、一次明細加總。
PDO ile 2 milyon satır: prepared statement cache sıfırlanınca ne oluyor
Geçen ay bir içe aktarma işini devraldım: PHP 8.2, MySQL 8.0, PDO mysql sürücüsü, tek bir worker. Girdi 2.1 milyon satırlık düz metin, satır başına bir UPDATE. İlk hali satır başına connect açıyordu;
PHP-FPM 慢日志里只看到 ? 时，我改用了 request_terminate_timeout
线上是 PHP 8.1 + PHP-FPM，前面挂 nginx，机器 8C16G，接口 QPS 峰值大概 300，单次响应 P99 在 800ms 左右。有天开始零星出现 502，频率不高，一天十几次，nginx error log 里是 upstream timed out。先去看 FPM 的 slowlog，request_slowlog_timeout 设的 5s，结果抓到的堆栈全是 `[p
PHP 8.3 の CLI で xdebug.mode=profile を本番相当データに当てたら遅すぎた話
PHP 8.3.4、Ubuntu 22.04、CLI からバッチスクリプトを叩く構成。DB から 40 万行を読んで集計し、結果を CSV に落とす処理で、本番相当のデータセットだと 1 実行 11 分かかっていた。ボトルネックの当たりを付けたくて、ローカルの同じデータで Xdebug のプロファイラを有効にした。
When PHP's unserialize silently truncated our 40MB session payload
PHP 8.2 on Ubuntu 22.04, PHP-FPM with Redis session handler, sessions stored via `session.serialize_handler = php`. A customer reported being logged out at random, roughly once a day, always after a l
France（Discussions：一个具体问题和一个不成熟的判断
最近在 France 上折腾 France（Discussions，遇到一个挺典型的情况：同一个做法在文档里看着没问题，换一个环境就要重来一遍。