Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.development.apps > #593

Re: Using Subversion (svn) to manage website files?

From Rainer Weikusat <rweikusat@mssgmbh.com>
Newsgroups comp.os.linux.misc, comp.unix.programmer, comp.os.linux.development.apps
Subject Re: Using Subversion (svn) to manage website files?
Date 2013-05-13 14:00 +0100
Message-ID <877gj3ghl1.fsf@sapphire.mobileactivedefense.com> (permalink)
References <kmdqli$bs8$1@dont-email.me> <kmqd3k$co1$1@dont-email.me>

Cross-posted to 3 groups.

Show all headers | View raw


David <david@55952163-3189045.bogus.domain.invalid> writes:

[...]


> I'm planning to use Subversion (svn) to manage and deploy website files
> on our development and live websites, but am new to Subversion and so
> would be very grateful for some advice..

[see original for details]

> So... (after a very long introduction) what I am wondering is how best
> to set up the file structure in our repository.
>
> With there being two separate websites (possibly, but not imminently 
> likely, others to follow later), I'm wondering whether they can even all
> co-exist in the same repository happily enough, or even whether I would
> be better asking for a separate repository for each.

I would put them into different repositories, if only to avoid the odd
effect that changes to 'website a' change the revision numbers of
'website b' files. 

> There's then the question of folder structure in the repository.
>
> Can I (sort of) "mirror" the webserver layout from the /data folder 
> downwards, bearing in mind that there exist existing files on the server 
> that must not be included in the repository and, equally importantly, 
> must not be overwritten when the repository contents are checked out or 
> updated onto the respective webservers?

You could create the intended directory structure and the versioned
files in svn, check that out and copy the 'alien files' to their
desired locations afterwards. Unless explicitly added to the
repository, subversion will ignore them by default. Another possible
idea would be to keep them in a separate tree and use (versioned)
symlinks in the 'managed' tree to refer to them.

Back to comp.os.linux.development.apps | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Using Subversion (svn) to manage website files? David <david@55952163-3189045.bogus.domain.invalid> - 2013-05-13 09:51 +0000
  Re: Using Subversion (svn) to manage website files? crankypuss <crankypuss@nomail.invalid> - 2013-05-13 05:16 -0600
  Re: Using Subversion (svn) to manage website files? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-05-13 14:00 +0100
  Re: Using Subversion (svn) to manage website files? Lusotec <nomail@nomail.not> - 2013-05-13 14:12 +0100
  Re: Using Subversion (svn) to manage website files? John Gordon <gordon@panix.com> - 2013-05-15 21:55 +0000

csiph-web