2016-02-27 34 views
1

以下是jekyll serve --verbose的輸出。正如你所看到的,Jekyll讀取4個降價文件,但實際上只生成了3. 2016-02-31-github-webhooks-node.md不是內置的,但似乎也沒有引發任何錯誤。爲什麼Jekyll會閱讀我的文章,但沒有編寫它們?

jekyll serve --verbose 
    Logging at level: debug 
Configuration file: /home/bryce/_repos/devbryce/devbryce-jekyll/_config.yml 
     Requiring: jekyll-paginate 
     Requiring: kramdown 
      Source: /home/bryce/_repos/devbryce/devbryce-jekyll 
     Destination: /home/bryce/_repos/devbryce/devbryce-jekyll/_site 
Incremental build: disabled. Enable with --incremental 
     Generating... 
      Reading: _posts/2013-12-31-whats-jekyll.md 
      Reading: _posts/2016-02-31-github-webhooks-node.md 
      Reading: _posts/2014-01-02-introducing-lanyon.md 
      Reading: _posts/2014-01-01-example-content.md 
     Rendering: _posts/2013-12-31-whats-jekyll.md 
    Pre-Render Hooks: _posts/2013-12-31-whats-jekyll.md 
    Rendering Liquid: _posts/2013-12-31-whats-jekyll.md 
    Rendering Markup: _posts/2013-12-31-whats-jekyll.md 
     Requiring: kramdown 
    Rendering Layout: _posts/2013-12-31-whats-jekyll.md 
     Rendering: _posts/2014-01-01-example-content.md 
    Pre-Render Hooks: _posts/2014-01-01-example-content.md 
    Rendering Liquid: _posts/2014-01-01-example-content.md 
     Requiring: rouge 
    Rendering Markup: _posts/2014-01-01-example-content.md 
    Rendering Layout: _posts/2014-01-01-example-content.md 
     Rendering: _posts/2014-01-02-introducing-lanyon.md 
    Pre-Render Hooks: _posts/2014-01-02-introducing-lanyon.md 
    Rendering Liquid: _posts/2014-01-02-introducing-lanyon.md 
    Rendering Markup: _posts/2014-01-02-introducing-lanyon.md 
    Rendering Layout: _posts/2014-01-02-introducing-lanyon.md 
     Rendering: 404.html 
    Pre-Render Hooks: 404.html 
    Rendering Liquid: 404.html 
    Rendering Markup: 404.html 
    Rendering Layout: 404.html 
     Rendering: about.md 
    Pre-Render Hooks: about.md 
    Rendering Liquid: about.md 
    Rendering Markup: about.md 
    Rendering Layout: about.md 
     Rendering: atom.xml 
    Pre-Render Hooks: atom.xml 
    Rendering Liquid: atom.xml 
    Rendering Markup: atom.xml 
    Rendering Layout: atom.xml 
     Rendering: index.html 
    Pre-Render Hooks: index.html 
    Rendering Liquid: index.html 
    Rendering Markup: index.html 
    Rendering Layout: index.html 
        done in 0.209 seconds. 
     Requiring: jekyll-watch 
     Requiring: jekyll-paginate 
     Requiring: kramdown 
      Watcher: Ignoring (?-mix:_config\.yml) 
      Watcher: Ignoring (?-mix:_site) 

2016-02-31-github-webhooks-node.md內容:

--- 
layout: post 
title: Setting up Github Webhooks with your Node app 
--- 

BLEEK BLOOP BLOP 

對於它的價值,這只是我對我自己創建的帖子。其餘的隨模板一起提供。

+0

使用有效日期,否則永遠不會發布! :) –

+0

我試過了,它會被Ruby解析爲3月2日。但是,我不會依賴那種保證行爲,充其量只是一個幸運的巧合。 –

回答

6

2016年2月31日,是

    在未來
  1. ,意味着該職位將只2016年二月,31日當天或之後公佈,除非你明確告訴傑奇否則(通過命令行或通過--future將其設置爲_config.yml
  2. 實際上並不存在,意味着它可能根本不會發布,但很可能會在3月2日發佈。
+1

'future:true' in'_config.yml' –

+0

謝謝 - 我的一個愚蠢的錯誤,雖然如果在這種情況發生時Jekyll拋出一個錯誤會很好。 –

+0

什麼時候會發生?一篇文章有​​未來的日期?這只是Jekyll的正常用法。您可以在將來發布帖子,並在該日期到達時發佈。或者當一個帖子有一個不存在的日期?我同意,應該報告。我猜Jekyll只是把日期交給Ruby的日期解析庫,遺憾的是允許這個。 –

相關問題