5 ms·
A simple example: if running your development server requires remembering several parameters for the command and possibly also requires starting up a database,
by jackowayed 15y ago
A simple example: if running your development server requires remembering several parameters for the command and possibly also requires starting up a database, that's annoying and may require you to look it up. Not a good starting-work experience
It feels unnecessary, but have a script called run in the root of your project that does that startup stuff. Then you just run ./run and it's time to code. No friction
- pbhjpbhj 15y ago>"have a script called run in the root of your project" // Bleurgh. Why not give it some sort of descriptive title? "./run-startup-actions-initialise-database.sh" would only need an extra keypress to start with shell completion active.
- phlux 15y agoI agree, though also I have found my self making aliases for lots of things and using them for a year on a box - then moving to a new machine/new job and not recalling how to do any of the things manually. Years ago, when I was at Lockheed, we had to do a bunch of stuff in support of devs - and after having them "train" us on the ridiculous install of their product, we wrote scripts and aliases to get the job done - but then after some time were wholly dependent on the scripts and couldnt do it by hand any loner.