🐧 Linux TippsDebian 11 Long Term Support reaches end-of-life(31.08.2026 um 02:00 Uhr)
🐧 Linux TippsUpdated Debian 13: 13.7 released(12.09.2026 um 02:00 Uhr)
🕵️ SicherheitslückenUSN-8741-1: Flatpak vulnerabilities(10.09.2026 um 10:44 Uhr)
🕵️ SicherheitslückenUSN-8742-1: Netty vulnerability(10.09.2026 um 11:01 Uhr)
🕵️ SicherheitslückenUSN-8737-2: GNU C Library vulnerabilities(10.09.2026 um 13:25 Uhr)
🕵️ SicherheitslückenUSN-8743-1: PHP vulnerabilities(10.09.2026 um 13:48 Uhr)
🕵️ SicherheitslückenUSN-8744-1: Python vulnerabilities(10.09.2026 um 15:53 Uhr)
🐧 Linux TippsUSN-8748-1: Linux kernel (NVIDIA) vulnerabilities(10.09.2026 um 17:32 Uhr)
🕵️ SicherheitslückenUSN-8745-1: KissFFT vulnerabilities(10.09.2026 um 17:36 Uhr)
🕵️ SicherheitslückenUSN-8746-1: libEBML vulnerability(10.09.2026 um 17:48 Uhr)
🐧 Linux TippsDebian 11 Long Term Support reaches end-of-life(31.08.2026 um 02:00 Uhr)
🐧 Linux TippsUpdated Debian 13: 13.7 released(12.09.2026 um 02:00 Uhr)
🕵️ SicherheitslückenUSN-8741-1: Flatpak vulnerabilities(10.09.2026 um 10:44 Uhr)
🕵️ SicherheitslückenUSN-8742-1: Netty vulnerability(10.09.2026 um 11:01 Uhr)
🕵️ SicherheitslückenUSN-8737-2: GNU C Library vulnerabilities(10.09.2026 um 13:25 Uhr)
🕵️ SicherheitslückenUSN-8743-1: PHP vulnerabilities(10.09.2026 um 13:48 Uhr)
🕵️ SicherheitslückenUSN-8744-1: Python vulnerabilities(10.09.2026 um 15:53 Uhr)
🐧 Linux TippsUSN-8748-1: Linux kernel (NVIDIA) vulnerabilities(10.09.2026 um 17:32 Uhr)
🕵️ SicherheitslückenUSN-8745-1: KissFFT vulnerabilities(10.09.2026 um 17:36 Uhr)
🕵️ SicherheitslückenUSN-8746-1: libEBML vulnerability(10.09.2026 um 17:48 Uhr)

🔧 Programmierung 🕛 vor 2 Monaten 3 Min Lesezeit
0

Stop copying config files into every new project — I built a CLI for this

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

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:




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





Add your reusable files to the collection:



CODE
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:



CODE
$ 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:



CODE
$ 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



CODE
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







GitHub logo



CLI for copying files from your private coffee collection into any project






coffee-installer
















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! 👇

Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Debian 11 Long Term Support reaches end-of-life
1 Quelle
Updated Debian 13: 13.7 released
1 Quelle
USN-8741-1: Flatpak vulnerabilities
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Stop copying config files into every new project — I built a CLI for this

Thematisch verwandte Begriffe: Stop, copying, config, files · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...