> Basically, I have a wrapper script deploy.sh that is run on macOS:
I do the same thing on Linux.
build.sh, deploy.sh.
But, I also use a run.sh which runs tasks that I may not remember to run if I come back to software after a while on a certain machine.
Like 'git pull' or 'bundle install'. Then ./dev-setup.sh or whatever for starting up tasks.
I use multiple machines and having these two simple commands saves me so much frustration.
You sit down to began work. You just run ./run.sh and it will setup a dev instance for you. No sudden alerts that your gem is out of date... or worse... no warnings at all and hard to diagnose sudden bugs that steals half a day from you.
I've found trying to figure out complicated build tools to mostly be a waste of time unless you really need them. It also encourages you to not do things that would require very costly builds.
I do the same thing on Linux.
build.sh, deploy.sh.
But, I also use a run.sh which runs tasks that I may not remember to run if I come back to software after a while on a certain machine.
Like 'git pull' or 'bundle install'. Then ./dev-setup.sh or whatever for starting up tasks.
I use multiple machines and having these two simple commands saves me so much frustration.
You sit down to began work. You just run ./run.sh and it will setup a dev instance for you. No sudden alerts that your gem is out of date... or worse... no warnings at all and hard to diagnose sudden bugs that steals half a day from you.