How can Zend Framework 2 be included in the draft version of Git?

How to manage versions of a Zend Framework 2 project? Is there a best practice / “standard approach” for this? Is the "submodule" the right keyword?

+5
source share
1 answer

A Zend Framework 2 project is usually a lightweight skeleton application with various modules installed, which are usually located in separate, dedicated repositories.

The main repository is usually not affected by many changes, so you can create a git repository (fork ZendSkeletonApplication ) for this. Although the modules are more relevant and require some caution, the skeletal application usually changes in only a few details over the course of a few months.

I can suggest the following approach:

  • create your first versions of application modules as git submodules in the directory of modules/your skeleton application fork.
  • work with modules in the proposed way, simply returning the original repositories and updating the links to the git submodules in the root repository.
  • ( composer zf2 ), , composer.json.
  • git zf2 . , . , . , , .
  • ( )

, . , , composer.json . Satis , .

, .

+5

All Articles