Accidentally pushed a .env file to GitHub? Here's the recommended recovery process

·1 views

Deleting a committed .env file does not erase the secret, since it remains in Git history and may already be cloned or forked. The recommended first step is to revoke and rotate the exposed credential at its provider, which neutralizes the leak immediately. Next, the file should be purged from every commit using git filter-repo, run in a fresh clone, with older filter-branch tutorials discouraged by the Git project. After verifying the cleanup, the rewritten history is force-pushed, a step that is irreversible and may trigger expected rejections for pull request references. Finally, developers are advised to contact GitHub Support for help with cached references and affected pull requests.

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)

InvoiceMate AI: A Local Open-Model Tool for Organizing Freelancer Expenses

InvoiceMate AI is a small expense organizer aimed at freelancers and tiny businesses that need to turn piles of invoices and receipts into clean records. Users paste or upload invoice text, and a local open-weight model running through Ollama extracts the vendor, date, amount, category, and description for review. Extracted entries are shown in an editable form before saving, and saved expenses appear on a dashboard with totals, a category chart, and a CSV export. The developer emphasizes privacy, since invoice text stays on the user's machine rather than going to a hosted AI service, though the project is an early MVP that holds data only in the browser session and does not support scanned-image OCR.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Keeping Original MRI Slices Distinguishable From AI-Generated Interpolations

A developer's exploratory MRI visualization project combined Python, AI-generated intermediate images, background transparency, and Blender. The article argues that generated slices can become indistinguishable from source images, making it harder to trace what came from the original data. It proposes keeping imported images in an immutable collection and writing derived results, masks, and generated layers separately with references to their sources. A manifest recording identifiers, ordering, spatial metadata, and processing settings is suggested, along with clearly marking generated images at creation. The piece also cautions that evenly stacked images do not establish physically accurate spacing and that generative interpolation is not the same as acquiring new observations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Tenant-Filtered Vector Search Needs Matching Embedding Models and Chunk-Level Freshness

The article argues that retrieval systems should embed user queries with the same model used for indexed help-center content and apply tenant constraints within the vector query itself. Filtering after a broad top-k search is described as flawed, since other tenants' chunks enter the candidate pool and displace permitted results. It recommends chunking content into answer-sized units and tracking chunk ID, tenant ID, source revision, and embedding model ID so changed material can be re-indexed selectively. The author also advises keeping telemetry lean, avoiding high-cardinality labels such as raw query text, full vectors, and tenant or chunk IDs. The piece frames these as correctness decisions that apply regardless of which vector database a team chooses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

RTX 3090 vs L40S: Relative Speed Depends on Batch Size, Study Finds

A developer measured an RTX 3090 against an L40S on rented machines using the same script, testing 7B fp16 models. The 3090 matched the L40S at batch size 1 (1.09x) but reached only 0.46x its speed at batch size 128. The author concluded there is no single speed figure, since relative performance depends on how many requests run concurrently. Cost was also factored in, with the 3090 rented at $0.414/h and the L40S at $0.826/h. The author noted that a different 3090 unit tested earlier was slower across all settings, so hardware should be measured per unit. All 192 runs and the script are published on GitHub.

0 comments Read more at DEV Community