dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make --config usage more explicit. 

See https://github.com/mojombo/jekyll/pull/965#discussion_r3797116 and https://github.com/mojombo/jekyll/pull/965#discussion_r3797085

Props @parkr.
This commit is contained in:
Benjamin J. Balter 2013-04-15 12:56:33 -04:00
parent 532adddbb8
commit db76121d89
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
site/_posts/2012-07-01-upgrading.md
View File

@ -28,12 +28,14 @@ Simply add the `--config` flag to the `jekyll` command, followed by the path
to one or more config files.
<div class="note info">
<h5 mardown="1">The `--config` flag overrides your `_config.yml` file</h5>
<h5 mardown="1">The `--config` explicitly specifies your configuration file</h5>
<p markdown="1">If you use the `--config` flag, Jekyll will ignore your
`_config.yml` file. Want to merge a custom configuration with the normal
configuration? No problem. Jekyll will accept more than one custom config
file via the command line. Simply pass the path to both files with the latter
file overriding the former.</p>
file via the command line. Config files cascade from right to left, such
that if I run `jekyll serve --config `--config _config.yml,_config-dev.yml`,
the values in the config files on the right (`_config-dev.yml`) overwrite
those on the left (`_config.yml`) when both contain the same key. , </p>
</div>
#### As a result, the following command line flags are now deprecated: