Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore *.gz files that are generated from 'rake assets:precompile' #3615

Closed
wants to merge 1 commit into from
Closed

Conversation

Alamoz
Copy link

@Alamoz Alamoz commented Nov 11, 2011

*.gz files generated from 'rake assets:precompile' are a hassle when deploying your rails app to a production server. These should be ignored by git.

@josevalim
Copy link
Contributor

Sorry, why are they a hassle?

@Alamoz
Copy link
Author

Alamoz commented Nov 12, 2011

OK, I see your point. I was having problems with git pulls on my production server, but thinking it through some files must have gotten out of sync. Logically, the files placed in /app/assets/ get assembled into files in /public/ and they should be the same on the dev server as on the prod server so it shouldn't cause a problem. Better, running 'rake assets:precompile' on the dev box and then pushing to prod server saves doing it there. I've just upgraded to Rails 3.1 and am still getting use to it.

@Alamoz Alamoz closed this Nov 12, 2011
@Alamoz
Copy link
Author

Alamoz commented Dec 3, 2011

Probably a good idea for people to .gitignore /public/ if they are using the asset pipeline, especially if they are doing some kind of content management where images are uploaded. They are likely not going to want to upload all the images on their development machine that they will have uploaded on their production server. So perhaps placing /public/ in .gitignore is a good default? Their stylesheets and javascripts will be version controlled under /app/assets/, so their code will maintain integrity that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants