据我所知,AWS弹性魔豆只需要一个单一的配置文件在 .elasticbeanstalk
目录,但(1),当我运行 EB配置
我得到一个额外的文件, myenv.env.yml
;和(2)我的IDE威胁附加文件作为重要推,通过将
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
!.elasticbeanstalk/*.cfg.yml
!.elasticbeanstalk/*.global.yml
在我的项目的的.gitignore
。
这些是什么额外的文件,不要他们发挥什么样的作用?我的理解是,仅的 config.yml
比什么都重要< /一>,那只有它有任何的影响。
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.
推荐答案
在 myenv.env.yml
文件旨在成为一个临时文件。 EB配置
创建它,那么你编辑,保存,并退出编辑器。一旦关闭编辑器,CLI将更新环境和该文件被删除。
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.
至于你的问题的第二部分,在的.gitignore
的部分是专为那些谁想要检查其配置。例如,假设你有一个 config.yml
文件。但是你要在你的团队的其他开发者使用该文件的标准版本。您可以创建(或重命名当前的文件) config.global.yml
称为文件,它会工作完全像 config.yml
,除了它可以在版本控制进行检查。
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.
如果你有一个 config.global.yml
和 config.yml
的 config.yml
将始终以precedence过任何重叠设置。
If you have a config.global.yml
and a config.yml
the config.yml
will always take precedence over any overlapping settings.
相关推荐
最新文章