version control - How can i work with SVN if not every one in group are -

version control - How can i work with SVN if not every one in group are -

i have tried setting logical way of using subversion (or other vcs i've played more svn).

let me start explaining problem, few coworkers needs changing our customers websites on daily basis, customers can alter files via "admin panel" on website. files generated on servers, logfile, export/import data, sitemaps etc.

we working on ftp, , maintain kind of file history create .bak.revision#.php files almost unmanagable. on top of using netbeans ide, requires local copies of files.

to start project need sync changed files client (or worst case download total project) (which can take forever).

i enjoy working netbeans, end using notepad++ instead.

i set pretty nice way of working svn post-commit hook exports project http folder way can update on local copy, create changes , commit -done-

but don't want overwrite files might have been changed on server, illustration customers css-file can create changes themselves.

so thought cannot 1 have problem, how work svn if not in team does? (in case customers)

i may able utilize svn:ignore on files guess?

(this test environment) post commit hook simple; svn export file:///svn/repo/live /var/www/html/ --force

edit plausible solution into, if create pre-commit, or improve ?pre-update? hook import overwrite files in repo, solve problem, not?

nvm import runs commit. commit , pre commit not work well, since create endless loop

kindest regards iesus

most logical , technical way in case (but not easiest) be

converting site tree working re-create of mutual (with netbeans) repository - require install subversion on server , post-install tricks, thus: ssh root-access host commit direct changes on site repo crontab job|special button in admin panel changing post-commit hook, which, in case, have update server's wc after commit "foreign" host

more exotic way: subversion (for users - behind scene)

everybody utilize subversion (directly) or indirectly - nobody touch files on site changes repository stored (as export) on site, happens now

for developers way alter nothing. technically mediocre customers you suggest, prepare , configure easysvn (and, therefore, assembla's repository) - they'll local folder (or tree), changes in (automagically) synced related repository (reverse direction work - background updates repo delivered wc). ssh or ftp tools of assembla space transfer changes site (automatically on commit or on demand hand)

svn version-control web