SShortSingh.
Back to feed

Dev Recovers Lost Gitea Data from Proxmox Backup After Docker Cleanup Mishap

0
·43 views

A home lab user accidentally wiped their Gitea instance's repositories and user data while running a routine Docker cleanup on a Lenovo M920q mini PC. The data loss stemmed from a misconfigured bind mount that pointed directly into Docker's internal volume storage, causing the cleanup process to delete the volume as if it were unused. Rather than restoring an entire VM from backup, the user surgically extracted the needed directory by decompressing a Proxmox VMA backup, mounting the raw disk image via loop device, and navigating the LVM structure to retrieve the intact files. A corrupted SQLite database — likely caused by the backup running mid-write — was repaired using SQLite's built-in recovery mode. The setup was subsequently rebuilt with volume paths stored on a Synology NAS instead of inside Docker's internal storage to prevent a recurrence.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Open-source project proposes AI agents clarify job roles before interviews

A maintainer of the open-source Agent Market project proposes using personal AI agents to clarify hiring conditions before candidates and teams invest time in interviews. The idea is presented as a hypothetical job-board alternative, not an available recruiting product. The proposed brief would cover employment type, deliverables, skills, hours, compensation and review process, with candidates controlling what they share. The author notes that Agent Market currently supports only free service-task trials, with payments and escrow not yet implemented, and that hiring workflows have not been tested as real recruitment transactions. The post also invites feedback on which unclear conditions waste the most time.

0
ProgrammingDEV Community ·

AI Tools Make Cloning Validated Indie Products Fast and Cheap, Threatening Creator Returns

Independent developers who spend months building and validating a product can see near-identical copies appear within days, often generated by AI coding agents that read a live interface and public copy. The article argues that once early revenue proves demand, that visibility makes the product an easier target for lookalike sites and automated distribution. It describes several patterns, including copies triggered by creator reviews, simple single-purpose utilities, template-based builds, and landing-page mimicry. It also notes that open demos and public sandboxes can leak the behaviors that copycats need to imitate. The author frames this as a structural change in software economics, where cheap replication weakens the returns creators earn from their innovation.

0
ProgrammingDEV Community ·

What rage prompts are and why they signal failed AI chats

A rage prompt is an angry or exasperated message a user sends to an AI after it has failed them, such as repeated demands, all-caps text, or insults. The habit of sending them is called rageprompting, and it usually follows several failed turns, marking the point where a user's patience ran out. They are a late signal, typically appearing after the user has already rephrased, corrected the AI, and waited. Because users who rage-prompt may decide the product cannot do the job, teams are advised to track them alongside other frustration signals. Detecting them reliably requires reading the preceding AI response, so a rules-based filter is paired with an LLM judge to confirm.

0
ProgrammingDEV Community ·

PNGDock Adds Browser-Local Batch Product Image Workflow Using Canvas and ZIP

A developer describes building a batch product image workflow for PNGDock that handles resizing, background color, format conversion, renaming, and downloading in one browser session. Image processing and ZIP creation run entirely in the browser, and selected images are not uploaded for this workflow. The tool accepts PNG, JPEG, and WebP files with explicit limits on batch size, file size, pixel count, and total ZIP output. Files are validated before queuing and processed sequentially, with bitmaps released after each encode to manage memory. The post stresses that a canvas background color is not background removal, and that PNG outputs get an extra optimization pass kept only when smaller.