Rake assets:precompile question

[Scott Shea]

What sort of issues am I looking at if I precompile locally and then check in my public/assets directory?

[Chad Woolley]

As a general rule of thumb, it's not a good practice to check in generated / derived files to source control.

1. Should be unnecessary, as long as you can reliably and repeatedly regenerate the same files in any environment which needs them

2. Creates unnecessary churn and work in source control.  You have to re-commit them every time they change.

Having said that, sometimes it's handy, especially if they change rarely.  E.g. on my project, we check them in on the release branch, because they almost never change.  When we make a new release branch, we just cherry-pick the commit from the prior branch.  The deploy is smart enough to not try to regenerate them if they're already checked in.

But I wouldn't do it on the mainline (master) branch.

-- Chad

On Wed, May 1, 2013 at 4:04 PM, Scott Shea <scott....@gmail.com> wrote:

What sort of issues am I looking at if I precompile locally and then check in my public/assets directory?

--
--
You are subscribed to the Google Groups "Phoenix Ruby Users Group" group.
To post, send email to phoeni...@googlegroups.com
To unsubscribe, send email to phoenix-ruby...@googlegroups.com
 
See http://rubyaz.org for group details
 
---
You received this message because you are subscribed to the Google Groups "Phoenix Ruby Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phoenix-ruby...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.