The best solution to something like this typically the simplest: Move static assets into a separate git repo, and symlink that into your website on deployments and whenever its actually needed. You don't want your git workflow to slow down for static assets that rarely change.
- Rob http://thinkrelevance.com http://runcoderun.com On Mon, Oct 20, 2008 at 12:31 PM, gwgeller <[EMAIL PROTECTED]> wrote: > > Hello, > I am fairly new to Git and Ruby On Rails. We are developing a > website that has thousands of images at maybe a dozen different sizes. > I believe there is close to 100,000 images in our image directory. So > all these images are in my ror folder and git repository. It is > slowing down everything like commits and pushes. Texmate pauses about > 3-4 seconds every time I click in it after it has lost focus. > The images aren't going to change that often so I don't need to push > them that often. My thought right now is to ignore my images directory > and manually push images. Or can I manage the images separate from git > altogether? My guess is no since git creates a new folder for each > deploy. I might be wrong on some of this. If anyone has any other > suggestions please let me know. > Thanks, > Gunner > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to github@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---