In the past when writing babushka deps, I'd need to commit and push
every tiny change manually, before rerunning the deps in my VM. It
always seemed like one too many switches and delays.
I've just found a setup that helps with that.
I run "asdf" on my dev machine to serve my babushka-deps directory on
port 9292 and add that local repo as the dep source in the VM
(something like `babushka sources -a ns
http://chris-berkhouts-macbook-pro-2.local:9292/.git`). That means I
don't have to push back to GitHub anymore.
Then I run "guard" in another terminal, with it set to commit and run
"git update-server-info" whenever files change. That saves me manually
committing on minor tweaks.
I'll do a "git rebase -i" when I've completed a larger unit of
changes, so I can squash the auto commits together and give them a
useful commit message.
Would anyone else find that setup useful?
If so I may extract it out into a gem so you just run one command to
turn on autocommit and repo serving.
Cheers.
Chris
Also, you don't need to use a prefix to run deps from ~/.babushka/deps.
./babushka-deps (i.e. within the current dir) is read from in the same way.
-Ben
> --
> To post, email babush...@googlegroups.com
> To unsubscribe, email babushka_app...@googlegroups.com
> ~
> http://babushka.me
> http://github.com/benhoskings/babushka
> http://groups.google.com/group/babushka_app
In the past I mounted the guest OS's dep directory on the host, but
the git update got in the way when going in that direction.
Cheers,
Chris