Server setup SVN


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
5 views
Bought VDS. I want to raise it to the SVN server (or git). And there are some features: svn will be used to develop web project, therefore the root of the repository must be the root of the website and after a commit should be immediately available in the browser (and it is good to rozdestvensky version on port 80 and 8080 for development). Also in the same root directory is the templates directory that you are working with a designer. So the designer should have access only to this folder, and programmers to all, including this one (if this is not possible, no problem to take the folder to another location, but still would like so). Finally, if possible, we would like to komitite and database (and also to have a release and development version).

That's just don't know how to implement such (never raised a version control system). Prompt?
by | 5 views

4 Answers

0 like 0 dislike
>>the root of the repository must be the root of the website and after a commit should be immediately available in the browser
\r
I will include the mode of boring and bring some clarity. The repository is not just a set of files and folders. The subversion repository uses organized in a special way the file system. Usually files are stored in the database, or the files of a certain format, so the root of the repository cannot be the root of the website.
\r
With regard to the use of project files for its intended purpose, it is necessary, first, to export a working copy(svn checkout). It is a common tree of folders and files with a hidden subdirectory .svn in each directory of the tree. Such a local copy is available to each project participant, who commits to the Central repository. But this copy cannot be used in production, because it contains these same service subdirectory .svn. In order to get rid of them, exported a clean working copy of the svn export. Now this is your project.
\r
Now is the time to develop a web project using svn, I can share how I have everything arranged.
VDS is on, where spinning the svn server. There are two branches of the repository trunk and release. On the local computer working copy as you develop comico all in the trunk. All scripts are tested for localhost. Development database the total, are located on the same server and svn.
by
0 like 0 dislike
1. Flies separately, cutlets separately
The root of the repository must not be the root of the website. The repository should have its own structure, with branches, etc.
\r
2. Automatic updates
Put a post-commit hook that after every commit will update the website. Anything difficult in it is not present, the documentation in Internet is.
\r
3. Data
There is already a need to write some scripts for removing the dump and to update it. You may also need a script that removes only a partial dump is critical for the application. Perhaps the best solution is a special software that supports database up to date.
by
0 like 0 dislike
Read the materiel on swnu, or you want to committing from an external svn repository in the website root?
by
0 like 0 dislike
There is not enough key words she Continuous Integration continuous build. ie we need an intermediate piece of software that automatically (or by pressing a single button) will deploy the website to the desired port. Ie, in your case, I would recommend to set two such scripts: the first commit deploys and restarts the site on a development port, and the second on "military" 80. Examples of such servers can be CruiseControl, Hudson...
each site will have its own directory and it is possible to configure Apache or IIS...
Think beyond yourself loosen our target keyword?
by

Related questions

0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
4 answers
0 like 0 dislike
2 answers
asked Mar 25, 2019 by Maxmyd
110,608 questions
257,186 answers
0 comments
27,917 users