惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
Hugging Face - Blog
Hugging Face - Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
WordPress大学
WordPress大学
Y
Y Combinator Blog
Google DeepMind News
Google DeepMind News
大猫的无限游戏
大猫的无限游戏
Vercel News
Vercel News
V
Visual Studio Blog
Microsoft Azure Blog
Microsoft Azure Blog
MyScale Blog
MyScale Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
罗磊的独立博客
N
Netflix TechBlog - Medium
M
MIT News - Artificial intelligence
G
Google Developers Blog
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
小众软件
小众软件
Engineering at Meta
Engineering at Meta
D
DataBreaches.Net
S
SegmentFault 最新的问题
H
Help Net Security
量子位

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Stop copying config files into every new project — I buil...
Ihda · 2026-06-19 · via DEV Community
Cover image for Stop copying config files into every new project — I built a CLI for this

Ihda

You know that feeling when you start a new project and spend
the first 20 minutes doing nothing productive?

Hunting for the Android keystore. Finding the right .env file.
Copying VS Code settings. Again. And again. Every. Single. Project.

I got tired of it. So I tried building something to fix it — coffee-installer.

How it works

Create a collection folder and point coffee-installer to it:

mkdir ~/.coffee-collection
echo '{ "baseSource": "~/.coffee-collection" }' > ~/.coffee.config.json

Add your reusable files to the collection:

mkdir -p ~/.coffee-collection/my-app/android/app
cp android/app/keystore.jks ~/.coffee-collection/my-app/android/app/
cp android/key.properties   ~/.coffee-collection/my-app/android/

Preview before installing:

$ coffee diff my-app
Diff — my-app (config)
  + add         android/key.properties
  + add         android/app/keystore.jks
  + add         frontend/.env.development.local
3 to add, 0 to overwrite, 0 to skip

Then install with one command:

$ coffee install my-app

📦 Installing my-app...
  ✅ copied android/key.properties
  ✅ copied android/app/keystore.jks
  ✅ copied frontend/.env.development.local
✅ my-app installed.

All commands

coffee list              # see everything in your collection
coffee diff my-app       # preview before installing
coffee install my-app    # install into current project
coffee pull my-app       # sync changes back to collection

Why I built this

I work across multiple projects — mobile apps, web backends, Flutter apps.
Every project needs the same credentials, the same IDE config, the same
environment files.

The alternative was a folder of files I'd manually copy every time, or
worse — storing credentials in a repo (never do this).

coffee-installer keeps everything in one local folder that never touches version control. It's not perfect yet, but it already saves me a lot of setup time.

Zero dependencies

The entire thing runs on Node.js stdlib only — no external packages,
nothing to audit, nothing that breaks when a dependency changes.

Try it

coffee-installer

npm version npm downloads license node zero dependencies

Stop copying the same config files into every new project.

coffee-installer lets you keep keystores, .env files, IDE settings, credentials, and any files you reuse across projects in one place — your coffee collection — and install them into any project with a single command.

coffee install my-app


Why

Every new project starts the same way: hunt for the .env file from the last project, find the Android keystore, copy the VS Code settings, remember where you put the Firebase credentials...

coffee-installer solves this by keeping all those files in a local collection folder and giving you a fast CLI to install, preview, and sync them.


Installation

npm install -g coffee-installer

Both coffee and coffee-installer are registered as CLI commands.


Demo

$ coffee list
Coffee Collection — ~/.coffee-collection

Config-defined projects:
  my-app     ~/.coffee.config.json
  backend    ~/.coffee.config.json

Folders in collection:
  .agents    (symlink)
  .vscode    (symlink)
  my-app     (config + convention)

⭐ Star coffee-installer on GitHub

I'm still figuring out the best workflow myself — how do YOU handle this?
I'd love to learn from how others solve it. Drop it in the comments! 👇