Nested version control scheme?

Question

Look for suggestions on how best to track this project structure in some form of version control (git or svn, preferably):

The project is intended for a web service that will have several versions of the "main" code, and users can create their own web service instance using any "kernel" that they would like (from the available versions). Thus, development / beta versions will exist on the same server as stable versions.

So, there are several “cores” that are likely to be different versions / tags / branches in version control. But then there is a comprehensive web interface that ties them together, which should be its own additional version control project for these web files.

From a structural point of view, it would look like this:

/-+
  |
  +--index.php
  +--engine/
  |  |
  |  +--1.0-stable/
  |  |  |
  |  |  +--feature.php
  |  +--2.0-beta/
  |     |
  |     +--feature.php
  +--main.css
  +--main.js

Thus index.php, main.cssthey main.jsare part of their own “project”, which is a web interface, and 2.0-betais a separate branch of development, updates of which will ultimately be merged into 2.0-stable, and any corrections for feature.phpin branch 1.0 should be combined into a file 2.0 feature.php.

Is it possible to create repositories inside repositories? How will this best manage?

Answer 1

, : . - ( ) , ( git svn: externals, SVN).

, , . , , .

Answer 2

, submodules .

Answer 3

. , subversion, ( git ), , , (svn cp). Subversion ( ), , . (subdir).

Answer 4

^ H ^ H ^ Hcode. , . , , .

( , ).

scm, , .

Answer 5

, . , :

/-+
  |
  +--discovery/
  |  |
  |  +--index.php
  |  +--main.css
  |  +--main.js
  +--engine/
     |
     +--1.0-stable/
     |  |
     |  +--feature.php
     +--2.0-beta/
        |
        +--feature.php

. . , , .

Deployments from version control will then be fairly standard for each engine version catalog.