Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9315625
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 19, 20262026-06-19T02:25:07+00:00 2026-06-19T02:25:07+00:00

We are in the process of moving our Drupal 6 sites into Git. I

  • 0

We are in the process of moving our Drupal 6 sites into Git. I noticed that Drupal 7 actually comes with a default .gitignore file which ignores the settings.php file and the sites/default/files directory. So I am assuming this is standard practice and that I should not version control the files directory. My question is though, what is the best method to move these files through the migration process from dev to test to live then? The live site may contain a ton of images in that directory that people have uploaded on the live site, but then the directory on the DEV server would have new images that some of the developers might have added to content they’ve created. Currently, when a content editor adds content in the way of a page node for example on the dev site, we have a WYSIWYG editor that allows them to upload an image that ends up in /sites/default/files/images and gets placed in their content. What is the easiest way to sync this files directory between the various servers?

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-19T02:25:08+00:00Added an answer on June 19, 2026 at 2:25 am

    Based on the response to @Brian’s answer above, the asker really has two questions:

    1. Why shouldn’t I include the files directory in source control
    2. Does the Deploy module support images uploaded by IMCE

    #1, Reasons why you shouldn’t include the files directory in source control:

    • @Brian gives reason #1 above, but it sounds like you do, in fact, push data from dev to prod.
    • The files directory isn’t well suited to source control. (Rarely do you want to revert or view commit history for the files directory)
    • The files directory can grow huge, which might become a repo storage problem
    • I usually symlink the files directory outside of the drupal install so I don’t need to move it if the server path changes (again, because it can be huge)
    • Many of the files in the files directory are likely to be derivatives of other files (in the case of image cache). Even if you were to justify putting the files directory under source control, it doesn’t make sense to keep track of /files/img.png and /files/imagecache/small/img.png.

    #2, Deploy module support for images:
    The short answer is no; Deploy does not support images uploaded by IMCE for D6. See: Add IMCE image support.

    But sarjeet.singh provides a patch for D7 in the issue linked to above. Given that the file directory paths are identical on dev/prod, you should be able to adapt it for Drupal 6.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Just in the process of moving part of our build server and found that
We are in the process of moving some software from our test environment into
I'm in the process of moving our Unity configuration to the web.config file. I'm
Our team is currently in the process of moving from SVN to Git. We
We're in the process of moving our SQL Server to it's own machine, but
I am in the process of moving some sites over to a new windows
Current Process: I have a tar.gz file. (Actually, I have about 2000 of them,
At our company we are moving from SvN to Git (yeah, better late than
As part of process improvements we are trying to ensure that all our projects
I'm currently in the process of moving from our own proprietary logging solution to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.