CODEWITHSUNDEEP
ruby-on-railsruby-on-rails-3asset-pipeline
dhulihan
dhulihan

Reputation: 11293

Should I precompile assets locallly before deployment on on the server?

I have the option to precompile my assets locally in development or on my production server. I deploy with git, so I'd prefer not to have to check in all these assets (especially if they're using cache-busting digests).

Is there any advantage to precompiling assets locally (other than lacking write-access on the production machine)?

Upvotes: 1

Views: 824

Answers (2)

rewritten
rewritten

Reputation: 16435

Your site doesn't need to be down when you precompile assets. If you use capistrano or similar tools, you precompile the assets in the server, then (after this and more steps have been completed) restart the app. Meanwhile the app is being served from the old code (and assets).

On the other side, I disagree about the "cache-busting" comment. Git is smart enough to understand a diff between two differently named files if possible. So the result would be exactly the same whether the names changed or not. In which case I completely agree that it's nonsensical to load the repository with generated data, like compiled assets.

Upvotes: 1

Edward
Edward

Reputation: 3499

I've found that compiling assets locally is much faster and then your site is down for a shorter period.

Of course, that depends on your server setup etc...

Upvotes: 1

Related Questions