How to Persist Claude CLI Session Login Across Docker Container Rebuilds

·3 views

Developers using Claude Code in Docker containers face a recurring login issue because the session file ~/.claude.json is not stored in a persistent volume, causing it to be wiped on every container rebuild. Since Docker named volumes back a directory rather than a single file, mounting a volume directly onto a file path fails. The workaround involves creating a dedicated directory, placing the session file inside it, and symlinking it back to the expected ~/.claude.json path in the home directory. A docker-compose volume is then mapped to that directory, and ownership is fixed via a post-install script to ensure the container user retains access. One caveat to watch for is atomic write behavior in apps, where a write-then-rename operation can silently replace the symlink with a plain file, breaking persistence without any error.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why One Sankey Diagram Can Replace Every Cloud Cost Spreadsheet

Cloud cost reviews often stall because billing data is stored as flat tables that only slice one dimension at a time, making it hard to trace how money flows across teams, accounts, and services. Tools like AWS Cost Explorer answer narrow queries quickly but cannot map the multi-dimensional paths that finance and engineering leaders actually need. Analysis of real cloud bills consistently reveals the same waste patterns: non-production environments running around the clock, 10–30% of spend with no ownership tag, zombie resources, oversized instances, and on-demand pricing for permanent workloads. Industry estimates have long placed overall cloud waste at roughly one-third of total spend, with losses concentrating wherever cost attribution is weakest. A Sankey diagram — which draws spending flows as ribbons scaled to dollar value — is proposed as the single visual that can show the full journey of a cloud dollar from invoice to team.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Silent Auth Bug Let Users Sign Up But Blocked Them From Ever Logging In

A developer working on a serverless .NET and AWS-based application discovered a subtle authentication bug where the signup process completed successfully, but users were ultimately unable to log in. The system sent a PIN via email and SMS as expected, yet the code did not match what AWS Cognito required when users attempted account confirmation. The root cause lay in a complex dual-Cognito-User-Pool architecture, where a shared user identifier could fall out of sync between the legacy pool, the newer authentication pool, and the application's own database. An asynchronous background task called SendingEmailsAfterApprovalBot, which ran every 15 minutes after account approval, created a timing window during which these systems could become misaligned. Because every individual step appeared to succeed, the bug was particularly difficult to detect and trace.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds free, no-signup AI text toolkit to cut sign-in friction

A developer created TextToolsAI, a free collection of single-purpose AI text tools — including rewriting, summarizing, and tone adjustment — requiring no account or payment. The project was motivated by frustration with existing tools that demand sign-ups or ad views even for quick, simple tasks. Built with Next.js, Vercel, and a backend LLM API, the app keeps API keys server-side and processes requests through route handlers for security. Each tool is defined as a configuration object rather than a hand-coded page, making it easy to scale the number of tools without added complexity. The developer has made the toolkit publicly available and is seeking feedback from other developers on output quality.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Cut Managed Database Costs Without Downtime or Re-Architecture

Cloud managed database bills — from RDS, Aurora, or Azure SQL — often grow unchecked because teams consider databases too critical to modify, but several low-risk, no-downtime optimizations can significantly reduce costs. The biggest savings typically come from storage hygiene: deleting unused audit tables and stale data in batches, reclaiming space via VACUUM on Postgres or index rebuilds on SQL Server, and dropping redundant indexes that slow writes without adding value. Instance rightsizing is another major lever; 30 days of CPU, memory, and connection metrics often reveal databases running on oversized instances chosen conservatively years ago, and Multi-AZ deployments allow class changes with only seconds of failover blip. Switching AWS storage from gp2 to gp3 can deliver the same performance at lower cost and is applied without downtime. Reserved Instances or Savings Plans should only be purchased after rightsizing is complete, to avoid locking in waste — and non-production databases running around the clock on production-grade instances represent a separate, often overlooked source of unnecessary spend.

0 comments Read more at DEV Community