阅读背景:

“config.yml”以外的文件在我的AWS EB配置中扮演什么角色?

来源:互联网 

I understand that AWS Elastic Beanstalk only needs a single configuration file in the .elasticbeanstalk directory, but (1) when I run eb config I get an additional file, myenv.env.yml; and (2) my IDE threats additional files as important to push, by placing

我知道AWS Elastic Beanstalk只需要.elasticbeanstalk目录中的单个配置文件,但是(1)当我运行eb config时,我得到一个额外的文件myenv.env.yml; (2)我的IDE通过放置来威胁其他重要文件

!.elasticbeanstalk/*.cfg.yml
!.elasticbeanstalk/*.global.yml 

in my project's .gitignore.

在我的项目的.gitignore中。

What are these additional files and what role do they play? My understanding was that only config.yml mattered, and that only it had any effect.

这些附加文件是什么以及它们扮演什么角色?我的理解是只有config.yml才有意义,只有它有任何影响。

1 个解决方案

#1


12  

The myenv.env.yml file is intended to be a temporary file. eb config creates it, then you edit it, save it, and exit the editor. Once the editor is closed, the CLI updates the environment and the file gets deleted.

myenv.env.yml文件旨在成为临时文件。 eb config创建它,然后编辑它,保存它,然后退出编辑器。关闭编辑器后,CLI将更新环境并删除文件。

As for the second part of your questions, the sections in .gitignore are intended for those who want to check in their configurations. For example, lets say you have a config.yml file. But you want other developers on your team to use a standard version of the file. You can create (or rename your current file) a file called config.global.yml and it will work exactly like config.yml except it can be checked in to version control.

至于问题的第二部分,.gitignore中的部分适用于那些想要检查其配置的人。例如,假设您有一个config.yml文件。但是您希望团队中的其他开发人员使用该文件的标准版本。您可以创建(或重命名当前文件)一个名为config.global.yml的文件,它的工作原理与config.yml完全相同,只是可以检入版本控制。

If you have a config.global.yml and a config.yml the config.yml will always take precedence over any overlapping settings.

如果您有config.global.yml和config.yml,则config.yml将始终优先于任何重叠设置。


分享到: