Dev workflow with Guard + Rake

[lynxbat]

Trying to switch my main workflow to use this possibly.

Added Rake tasks for syncing local Razor src (On my Mac in my case) into the [gold] VM and then into /opt/Razor.

Added Guardfile with watchers for watching src under src/Razor locally.

End result is as files are updated in local editor (RubyMine in my case) they are automatically synced into the [gold] VM so I can run tests immediately.

Couple things around why I did this a certain way:

1. I sync into /tmp/src_sync and then 'sudo mv' into /opt/Razor. This is because the vagrant-sync gem doesn't have a way to easily use the root account or sudo. And changing the Razor permissions inside the [gold] VM is nasty. So instead I sync using 'vagrant' user with vagrant-sync. And then use the ssh method to run the 'sudo cp -r' to overwrite updated files.
2. I broke up each subfolder into separate sync tasks and watchers to save CPU and unnecessary copying.
3. You have to have your Razor source git repo in src/Razor. I tried to make this work well with another path. but getting Guard to follow symlinks reliably or modifying Listen gem to monitor a different path felt wonky.

Also, added correct link to Scientific Linux as it was an MK ISO link before.

LMK what you think.

[benburkert]

This is really cool. I think it will drop the barrier to entry for developers who want to hack on Razor, myself included. But I'd like to keep this repo as demo/tutorial for Razor. Maybe it's time to fork this and restructure it as developer sandbox for Razor. Thoughts?

Also, I'm gonna cherry pick in the Scientific Linux fix.

[lynxbat]

Yeah. How do you want to fork or clone?

Want me to host? Would make sense to rename which would be a clone to new repo name?

[benburkert]

Yeah, i think it makes sense for you to own the fork. I wouldn't worry about keeping them compatible, i'll follow along and cherry pick anything worth bringing over into this project.