5 ms·
I think I'll stick with `brew upgrade` or, more accurately, brew update brew upgrade npm -g upgrade for f in ~/projects/*; do cd $f
by matt4077 10y ago
I think I'll stick with `brew upgrade` or, more accurately,
brew update
brew upgrade
npm -g upgrade
for f in ~/projects/*; do
cd $f
npm update --save
npm update --save-dev
mix deps.update --all
elm-packages update
bundle update
npm test
mix test
rake test
done
- guessmyname 10y ago# I fixed the script for you: [...] for f in $(ls -1d ~/projects/**/); do cd -- "$f" [...] done
- Jtsummers 10y ago[...] pushd . for [...] popd I'm always a fan of ending up back where I started.
- thomaslee 10y agoPiling on the nitpick train :) If an error occurs along the way popd won't run, so a subshell might be a better way to accomplish the same thing: ( for ...; do cd ... done ) # script exits, you're back where you started If you'd prefer to see it in isolation: pwd; ( cd /tmp; pwd ); pwd