简体繁体 English

使用Git的Sylius / Symfony标准版本控制流程

[英]Sylius / Symfony standard version control flow using Git

原文 2018-05-17 01:57:53 8 1 git/ symfony/ sylius

Could anyone provide the correct version control flow of Sylius / Symfony? 谁能提供Sylius / Symfony的正确版本控制流程？ (I am now to Symfony / Sylius.) （我现在去Symfony / Sylius。）

I have setup a UAT server for Sylius and would like to have development server on my own environment. 我已经为Sylius设置了UAT服务器，并且希望在自己的环境中安装开发服务器。 Should I create a git repo from UAT and then install sylius on my environment and pull from git? 我应该从UAT创建一个git repo，然后在我的环境中安装sylius并从git中提取吗？

What are the files should be included in git? git中应包含哪些文件？ Sylius already included gitignore file but seems some of them should ignore (eg: /web/) Should I just git /app/ ? Sylius已经包含了gitignore文件，但是似乎其中一些应该忽略（例如：/ web /），我应该只是git / app /吗？

1 个解决方案

I think you should take a look at Composer first. 我认为您应该先看看Composer。 Unless the previous maintainers did something weird, all dependencies (amongst which Sylius and Symfony) are defined and required via Composer and installed via composer install in the vendor folder. 除非以前的维护者做过一些奇怪的事情，否则所有依赖项（在Sylius和Symfony中）都通过Composer定义和要求，并通过composer install在vendor文件夹中。

Except the vendor folder, everything else should be versioned. 除vendor文件夹外，其他所有版本均应进行版本控制。 Only, don't store passwords in Git; 只有，不要在Git中存储密码； use a git-ignored parameters.yml or even better environment variables. 使用忽略git的parameters.yml甚至更好的环境变量。 See http://symfony.com/doc/current/best_practices/configuration.html for a full explanation. 有关完整说明，请参见http://symfony.com/doc/current/best_practices/configuration.html 。