Another option I've seen sites with large image sets use is to push everything onto another sub-domain. static.mydomain.com. Then you simply point every image ref to that server. You can optimize that server for serving static files, and you don't muck up your main server or main repo with a ton of static files. --tek
On Wed, Oct 22, 2008 at 10:59 AM, Markus Prinz < [EMAIL PROTECTED]> wrote: > > > On 22.10.2008, at 17:55, gwgeller wrote: > > > > > Rob, > > I may have misunderstood. I setup a symlink in my development > > environment but that basically creates the same issue. Are you saying > > only setup the symlink when deploying? I need the images for > > development too though. > > I think he meant using a symlink, but adding the link to > the .gitignore file so it doesn't get checked in. But you'd also have > to do that whenever someone creates a new clone, so this solution is a > bit suboptimal. > > Submodules[0] might be a better solution to your problems. > > g, Markus > > [0] http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
