Home/ Questions/Q 6602903
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T18:56:06+00:00

I have a setup like this. SVN Repository Live Site Dev Site Local Copy

  • 0

I have a setup like this.

  1. SVN Repository
  2. Live Site
  3. Dev Site
  4. Local Copy

SVN Repository is identical to Live site.
Every different sites have different config file, local.xml.
Some clients are windows/toitoise and some clients are linux servers which I have SSH access to.

My requirements are.

  1. I don’t want local.xml to be changed neither on A. Repository when committing nor B. clients when updating.

  2. I want local.xml to be part of every new checkouts.

  3. I don’t want local.xml files on clients lingering “modified” with question mark signs after being modified.

  4. I don’t want to manually “uncheck” local.xml on every commit as there are some more folders like cache and image files to be “ignored” too.

I’ve tried,
– Locking the file on Repo. That throws an ugly error when committing. I’m afraid it would break the rest of commits.
– SVN:ignore local.xml. But seems it’s still going through.

Thanks for your help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Having the file in the ignore list is needed, but it alone will not do the trick. You’ll also need to delete the file from the repository. Run this to delete the file from SVN but keep the local file:

    svn rm --keep-local local.xml
svn commit

    EDIT: A common way to keep local settings files in SVN is adding them with names like default.local.xml and copying them to local.xml and modifying the settings right after the first checkout. This way you won’t risk overwriting of conflicting your actual settings file.

    • 0