Hacker News new | ask | show | jobs
by tracker1 15 hours ago
I've been doing similar for many scripts within project workflows... I've started calling the directory in question ./run/ by convention, so I type run/scriptname to run stuff... I've got bash (extnsionless) and powershell (ps1) scripts in place on my work project).

I'll also lean into docker+compose usage for any background services, and even development in order to reduce the running footprint switching projects.
1 comments
grepsedawk 13 hours ago
Love it! Same here. bin/ is a convention I picked up from Rails and thoughtbot over the years. I also have bin/staging and bin/prod for data fixes, deploy helpers, and querying the DB, alongside bin/test and bin/dev.
link
tracker1 13 hours ago
Yeah, I've used bin/ and scripts/ in the past as well as _scripts/ ... but I just like the ergonomics of run/foo... run/api, run/ui, run/api-test, ... etc.

I'm usually working in a subproject, so it's usually ../../run/foo in practice, but still.

link
grepsedawk 13 hours ago
Yeah! All the same. I love this pattern.
link