Manual testing is teh suck. I could write some integration tests (in my less than standard style), but @parkr do you think you give this a shot? I can help out once you get the ball rolling.

Set "published": true (or remove "published" variable)
If the post has been unpublished (published: false) in frontmatter and we want to publish it, then we need to set "published": true (or remove "published" variable)

Would it be trivial to add a line to _octopress.yml (on octopress init perhaps?) which indicates the base working directory on the local filesystem? This would avoid the admittedly minor problem that I'm sure we've all had of running octopress build in an arbitrary directory that we've been working in (_include, _templates etc.) and running into errors or creating _site directories everywhere that we have to delete.

Migrated from Octopress 2.0.

STEPS TO REPRODUCE

• Made a new clean directory.
• copied my _config.yml
• Copied my old posts
• octopress build

RESULT
octopress 3.0.0.rc.12 | Error: undefined method `published'

It give this error on all off my posts

Core

• Add new posts & pages (dates, yaml front-matter defaults)
• Working with drafts (_drafts)
• Pass commands we don't know to jekyll

External

• Octopress deployments

I like the ability to create drafts, but I do not see how to preview them. They don't show up when I do jekyll serve and the isolate command can't find a draft.

So, am I just using drafts wrong or is there a command that I'm missing?

octopress publish --help claims that the default value for --date is now:

$ octopress publish --help
...
Options:
  --date DATE    String that is parseable by Time#parse. (default: Time.now.iso8601)

I thought this would mean that unless --date is specified, any drafts are published with with the current time as their date. However, this is incorrect; if --date isn't specified, the draft is published using the date already specified in its frontmatter. To publish a draft with a date of now, you must use --date now.

It doesn't seem meaningful to say that the default for --date is now, since --date has no effect unless specified.

I haven't updated my Octopress for at least a month. After updating the bundle for my site today I got the error
" Liquid Exception: Unknown tag 'endraw' in _posts/2004-02-07-....."

To make sure that not any other updated gem caused this problem I played around with the dependencies in my Gemfile and arrived at the following Gemfile.lock which works

GEM
  remote: http://rubygems.org/
  specs:
    blankslate (2.1.2.4)
    celluloid (0.16.0)
      timers (~> 4.0.0)
    classifier-reborn (2.0.1)
      fast-stemmer (~> 1.0)
    coffee-script (2.3.0)
      coffee-script-source
      execjs
    coffee-script-source (1.8.0)
    colorator (0.1)
    execjs (2.2.1)
    fast-stemmer (1.0.2)
    ffi (1.9.6)
    hitimes (1.2.2)
    jekyll (2.4.0)
      classifier-reborn (~> 2.0)
      colorator (~> 0.1)
      jekyll-coffeescript (~> 1.0)
      jekyll-gist (~> 1.0)
      jekyll-paginate (~> 1.0)
      jekyll-sass-converter (~> 1.0)
      jekyll-watch (~> 1.1)
      kramdown (~> 1.3)
      liquid (~> 2.6.1)
      mercenary (~> 0.3.3)
      pygments.rb (~> 0.6.0)
      redcarpet (~> 3.1)
      safe_yaml (~> 1.0)
      toml (~> 0.1.0)
    jekyll-coffeescript (1.0.1)
      coffee-script (~> 2.2)
    jekyll-gist (1.1.0)
    jekyll-paginate (1.0.0)
    jekyll-sass-converter (1.2.1)
      sass (~> 3.2)
    jekyll-tagging (0.6.0)
      ruby-nuggets
    jekyll-watch (1.1.1)
      listen (~> 2.7)
    json (1.8.1)
    kramdown (1.4.2)
    liquid (2.6.1)
    listen (2.7.11)
      celluloid (>= 0.15.2)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
    mercenary (0.3.4)
    nuggets (1.0.0)
    octopress (3.0.0.rc.14)
      jekyll (~> 2.0)
      mercenary (~> 0.3.2)
      titlecase
    octopress-asset-pipeline (1.0.4)
      octopress-ink (~> 1.0.0.rc.15)
    octopress-date-format (2.0.1)
      jekyll (~> 2.0)
      octopress-hooks (~> 2.0)
    octopress-deploy (1.0.0.rc.10)
      colorator
      octopress (~> 3.0.0.rc.10)
    octopress-filters (1.2.0)
      jekyll
      octopress-hooks (~> 2.0)
      rubypants-unicode
      titlecase
    octopress-hooks (2.2.1)
      jekyll (~> 2.0)
    octopress-include-tag (1.0.0)
      jekyll (~> 2.0)
      octopress-tag-helpers (~> 1.0)
    octopress-ink (1.0.0.rc.17)
      jekyll (~> 2.0)
      octopress
      octopress-filters (~> 1.1)
      octopress-hooks (~> 2.2)
      octopress-include-tag (~> 1.0)
      uglifier (~> 2.5)
    octopress-tag-helpers (1.0.2)
      jekyll (~> 2.0)
    parslet (1.5.0)
      blankslate (~> 2.0)
    posix-spawn (0.3.9)
    pygments.rb (0.6.0)
      posix-spawn (~> 0.3.6)
      yajl-ruby (~> 1.1.0)
    rb-fsevent (0.9.4)
    rb-inotify (0.9.5)
      ffi (>= 0.5.0)
    redcarpet (3.1.2)
    ruby-nuggets (1.0.0)
      nuggets (= 1.0.0)
    rubypants-unicode (0.2.5)
    safe_yaml (1.0.4)
    sass (3.4.5)
    timers (4.0.1)
      hitimes
    titlecase (0.1.1)
    toml (0.1.1)
      parslet (~> 1.5.0)
    uglifier (2.5.3)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    yajl-ruby (1.1.0)

PLATFORMS
  ruby

DEPENDENCIES
  jekyll-tagging
  octopress (= 3.0.0.rc.14)
  octopress-asset-pipeline
  octopress-date-format
  octopress-deploy (= 1.0.0.rc.10)
  octopress-ink (= 1.0.0.rc.17)

and this one that produces the error:

GEM
  remote: http://rubygems.org/
  specs:
    blankslate (2.1.2.4)
    celluloid (0.16.0)
      timers (~> 4.0.0)
    classifier-reborn (2.0.1)
      fast-stemmer (~> 1.0)
    coffee-script (2.3.0)
      coffee-script-source
      execjs
    coffee-script-source (1.8.0)
    colorator (0.1)
    execjs (2.2.1)
    fast-stemmer (1.0.2)
    ffi (1.9.6)
    hitimes (1.2.2)
    jekyll (2.4.0)
      classifier-reborn (~> 2.0)
      colorator (~> 0.1)
      jekyll-coffeescript (~> 1.0)
      jekyll-gist (~> 1.0)
      jekyll-paginate (~> 1.0)
      jekyll-sass-converter (~> 1.0)
      jekyll-watch (~> 1.1)
      kramdown (~> 1.3)
      liquid (~> 2.6.1)
      mercenary (~> 0.3.3)
      pygments.rb (~> 0.6.0)
      redcarpet (~> 3.1)
      safe_yaml (~> 1.0)
      toml (~> 0.1.0)
    jekyll-coffeescript (1.0.1)
      coffee-script (~> 2.2)
    jekyll-gist (1.1.0)
    jekyll-paginate (1.0.0)
    jekyll-sass-converter (1.2.1)
      sass (~> 3.2)
    jekyll-tagging (0.6.0)
      ruby-nuggets
    jekyll-watch (1.1.1)
      listen (~> 2.7)
    json (1.8.1)
    kramdown (1.4.2)
    liquid (2.6.1)
    listen (2.7.11)
      celluloid (>= 0.15.2)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
    mercenary (0.3.4)
    nuggets (1.0.0)
    octopress (3.0.0.rc.15)
      jekyll (~> 2.0)
      mercenary (~> 0.3.2)
      octopress-deploy
      octopress-docs
      titlecase
    octopress-asset-pipeline (1.0.4)
      octopress-ink (~> 1.0.0.rc.15)
    octopress-date-format (2.0.1)
      jekyll (~> 2.0)
      octopress-hooks (~> 2.0)
    octopress-deploy (1.0.0)
      colorator
      octopress-docs
    octopress-docs (0.0.9)
      jekyll (~> 2.0)
      octopress-escape-code (~> 1.0)
      octopress-hooks (~> 2.0)
    octopress-escape-code (1.0.2)
      octopress-hooks (~> 2.0)
    octopress-filters (1.2.0)
      jekyll
      octopress-hooks (~> 2.0)
      rubypants-unicode
      titlecase
    octopress-hooks (2.2.1)
      jekyll (~> 2.0)
    octopress-include-tag (1.0.0)
      jekyll (~> 2.0)
      octopress-tag-helpers (~> 1.0)
    octopress-ink (1.0.0.rc.18)
      jekyll (~> 2.0)
      octopress (~> 3.0.0.rc)
      octopress-docs
      octopress-filters (~> 1.1)
      octopress-hooks (~> 2.2)
      octopress-include-tag (~> 1.0)
      uglifier (~> 2.5)
    octopress-tag-helpers (1.0.2)
      jekyll (~> 2.0)
    parslet (1.5.0)
      blankslate (~> 2.0)
    posix-spawn (0.3.9)
    pygments.rb (0.6.0)
      posix-spawn (~> 0.3.6)
      yajl-ruby (~> 1.1.0)
    rb-fsevent (0.9.4)
    rb-inotify (0.9.5)
      ffi (>= 0.5.0)
    redcarpet (3.1.2)
    ruby-nuggets (1.0.0)
      nuggets (= 1.0.0)
    rubypants-unicode (0.2.5)
    safe_yaml (1.0.4)
    sass (3.4.5)
    timers (4.0.1)
      hitimes
    titlecase (0.1.1)
    toml (0.1.1)
      parslet (~> 1.5.0)
    uglifier (2.5.3)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    yajl-ruby (1.1.0)

PLATFORMS
  ruby

DEPENDENCIES
  jekyll-tagging
  octopress (~> 3.0.0.rc.12)
  octopress-asset-pipeline
  octopress-date-format
  octopress-deploy (~> 1.0.0.rc.10)
  octopress-ink

Does it help in finding the problem? BTW: Here's the stack trace on this error:

/Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/block.rb:62:in `unknown_tag': Unknown tag 'endraw' (Liquid::SyntaxError)
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/block.rb:32:in `parse'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/document.rb:5:in `initialize'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/template.rb:59:in `new'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/template.rb:59:in `parse'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/liquid-2.6.1/lib/liquid/template.rb:46:in `parse'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/convertible.rb:106:in `render_liquid'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/convertible.rb:233:in `do_layout'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/octopress-hooks-2.2.1/lib/octopress-hooks.rb:223:in `do_layout'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/post.rb:261:in `render'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/site.rb:269:in `block in render'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/site.rb:268:in `each'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/site.rb:268:in `render'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/octopress-hooks-2.2.1/lib/octopress-hooks.rb:138:in `render'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/site.rb:46:in `process'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/command.rb:28:in `process_site'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/commands/build.rb:55:in `build'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/jekyll-2.4.0/lib/jekyll/commands/build.rb:33:in `process'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/octopress-3.0.0.rc.15/lib/octopress/commands/serve.rb:23:in `block (2 levels) in init_with_program'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary/command.rb:220:in `call'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary/command.rb:220:in `block in execute'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary/command.rb:220:in `each'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary/command.rb:220:in `execute'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary/program.rb:35:in `go'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/mercenary-0.3.4/lib/mercenary.rb:22:in `program'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/gems/octopress-3.0.0.rc.15/bin/octopress:18:in `<top (required)>'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/bin/octopress:23:in `load'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/bin/octopress:23:in `<main>'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `eval'
    from /Users/robertbeeger/.rvm/gems/ruby-2.1.1/bin/ruby_executable_hooks:15:in `<main>'

I'm a relative {non-hacker) newbie to Octopress.

I'm getting the Error Message below when performing a "rake generate"

The only thing I've done since my last "rake generate" was to update Brew, with associated commands: brew doctor; brew upgrade (I think) ; and brew prune

(I'm a novice with Brew, too. As best I remember, "brew prune" removed "dead symlinks.")

....

HMacBook-3:~ howardm$ cd octopres
Using /Users/howardm/.rvm/gems/ruby-1.9.3-p392 with gemset octopress
HMacBook-3:octopres howardm$ rake generate

Generating Site with Jekyll

unchanged sass/screen.scss
Configuration from /Users/howardm/octopres/_config.yml
/Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/openssl.rb:17:in require': dlopen(/Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/x86_64-darwin12.2.1/openssl.bundle, 9): Symbol not found: _SSLv2_client_method (LoadError) Referenced from: /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/x86_64-darwin12.2.1/openssl.bundle Expected in: flat namespace in /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/x86_64-darwin12.2.1/openssl.bundle - /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/x86_64-darwin12.2.1/openssl.bundle from /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/openssl.rb:17:in<top (required)>'
from /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/https.rb:22:in require' from /Users/howardm/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/net/https.rb:22:in<top (required)>'
from /Users/howardm/octopres/plugins/gist_tag.rb:10:in require' from /Users/howardm/octopres/plugins/gist_tag.rb:10:in<top (required)>'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:78:in require' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:78:inblock (2 levels) in setup'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:77:in each' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:77:inblock in setup'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:76:in each' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:76:insetup'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/lib/jekyll/site.rb:31:in initialize' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/bin/jekyll:238:innew'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/gems/jekyll-0.12.0/bin/jekyll:238:in <top (required)>' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/bin/jekyll:19:inload'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/bin/jekyll:19:in <main>' from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/bin/ruby_noexec_wrapper:14:ineval'
from /Users/howardm/.rvm/gems/ruby-1.9.3-p392@octopress/bin/ruby_noexec_wrapper:14:in `

........

Can anyone provide me with guidance about fixing this ?

Thanks!

Howard

I have a post template where I want to generate a random hex identifier for each post. The template is simple:

---
layout: {{ layout }}
identifier: {% random_hex %}
title: {{ title }}
date: {{ date }}

---

where random_hex is a working liquid plugin found in my source/_plugins directory. But when running: octopress new post, I get a crash on this line complaining: Unknown tag 'random_hex' (Liquid::SyntaxError)

I can use this tag in my posts and view so I know it's working, but it appears that Octopress does not load the _plugins directory prior to running the new generation. How can this be resolved?

I gave Octopress 3 a spin. (I’m a happy Octopress 2 user, but not a Jekyll or Ruby expert by any means.) I managed to get it installed, but not sure what to do next. In an empty folder, I can generate some post markdown files with octopress new post command, but it is not clear how those turn into pages.

As a user, I’m expecting to follow a set of instructions that help me get started from scratch and don’t assume any prior knowledge about Jekyll or anything else. The steps would be roughly like this…

• Install (already partly covered by current readme… it covers installing the octopress command, but not how to init a site. What’s the difference between octopress init and octopress new?)
• Create and edit a new page/post (sort of covered, I could figure it out based on readme)
• Build the site HTML (missing. If I didn’t do init or new, I just have a _posts folder by this point. How does that turn into HTML?)
• Serve a site preview
• Load the site from a localhost URL in the browser and see something that looks like a site.

This will prevent this error:

Forbidden
no access permission to `/'

Reference jekyll/jekyll#1293

when I run octopress build,there is nothings output,How can I build ?

Hi Brandon, it looks like the instructions in the readme don't work anymore..

+✔ ~/Development  octopress new myblog
New jekyll site installed in /Users/johnmorales/Development/myblog.
octopress 3.0.0.rc.24 | Error:  No such file or directory @ rb_file_s_stat - /Users/johnmorales/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/octopress-3.0.0.rc.24/scaffold/.
+✔ ~/Development

In order to release 3.0, we have some work ahead of us:

• jekyll-paginate needs to be reworked per octopress/ink#23
• Write octopress integrate
• Write octopress isolate
• image tag plugin
• pull_quote tag plugin
• video tag plugin
• Documentation!

Anything else, @imathis? If we can get a comprehensive list here, then we can move forward more swiftly. Async.

if the command octopress -h is run there are duplicates shown for the serve and doctor subcommands.

$ octopress -h
octopress 3.0.0.alpha6 -- Octopress is an obsessively designed toolkit for Jekyll blogging.

Usage:

  octopress <subcommand> [options]

Options:
        -h, --help         Show this message
        -v, --version      Print the name and version
        -t, --trace        Show the full backtrace when an error occurs

Subcommands:
  new                   Creates a new Jekyll site scaffold in PATH
  publish               Convert a draft to a normal published post.
  build                 Build your site
  serve                 Serve your site locally
  serve                 Serve your site locally
  doctor                Search site and print specific deprecation warnings
  doctor                Search site and print specific deprecation warnings
  docs                  Soon: Launch local server with docs for Octopress v3.0.0.alpha6
  deploy                Deploy your Octopress site.

I am about to start a new site / blog project. It's a paying gig, so I don't have the luxury of waiting. I want to go static generator for this project and after reviewing a bunch of different ones, I had decided to make a first try with Octopress, looking for a headstart and somewhat quicker "onramp" over using Jekyll alone. I started on the octopress.org site, looking at 2.0 and then in the course of due diligence (before I started building anything), found my way here to v 3.0.

I have done blogs with other static generators before (python ones and I am a python developer), but have no prior experience with Octopress or Jekyll.

I'm a hacker / developer, but not much of a ruby guy (I can install gems...).

So here are a few questions:

1. At first, all I am really going to need is basic blog functionality with Disqus. Does version 3.0 currently help with that stuff over and above a generic Jekyll install?
2. I'll be building a custom theme for the project and that's what I will start working on first thing. Is there anything I should know if I do this starting with 3.0 as it currently sits?
3. Does anyone here know of a basic tutorial for starting a new project (not a migration) from scratch with v 3.0?

Subject says it all. Is there a doc? I can't seem to find it (but then again I've only had one coffee so far.)

Thanks,
-kevin

I am getting the above error when generating using rake generate

My problem seems to be here
imathis/octopress#1635
but it does not work out

has renewed 'gem' (still error)
already downgrade 'Jekyll' (still error), 'Jekyll' before this incident is 2.5.0
even until there is a gem that I delete, because before this there is a command to 'cleanup'

what should i do
any help would be appreciated

When I run octopress watch, nothing is printed, and when I run octopress watch --help, it prints the same help message as for octopress --help. Is there no Octopress equivalent of jekyll --watch? Are there substantial drawbacks to just using jekyll watch instead?

I know this is alpha software, so not sure if this is a known issue or not, but octopress new page "title of page" doesn't respect the template in _templates - it misses out the excerpt: and tags: YAML keys. Just delete this if it's a known problem!

I'm really excited to start testing out the release candidate!

Found a minor issue, when I run Octopress help, the serve and doctor subcommands are listed twice:

$ octopress --help
octopress 3.0.0.rc.3 -- Octopress is an obsessively designed toolkit for Jekyll blogging.

Usage:

  octopress <subcommand> [options]

Options:
        -h, --help         Show this message
        -v, --version      Print the name and version
        -t, --trace        Show the full backtrace when an error occurs

Subcommands:
  new                   Creates a new Jekyll site scaffold in path.
  init                  Add Octopress's default scaffolding to your site.
  publish               Convert a draft to a normal published post.
  build                 Build your site
  serve                 Serve your site locally
  serve                 Serve your site locally
  doctor                Search site and print specific deprecation warnings
  doctor                Search site and print specific deprecation warnings

Perhaps an issue involving mercenary? I haven't yet tried to identify what's causing it.

When the --watch flag is specified it continually regenerates.

I set up a default install and created a blog post. Then decided to change the theme.

I changed it to OctoFound https://github.com/annejohnson/octofound then changed it back to the default theme.

But I guess OctoFound changed files permanently. http://jhwhite.github.io.

Is there a way to undo what OctoFound did? Or can I use GitHub to go to a previous commit or something?

Octopress deploy is a gem I've created to manage deployment of static sites. Integrating it should allow us to maintain the deployment separately from the CLI and allow people to use the deployment without the CLI.

I'm not certain what the best way would be to pass options to deploy, but since it relies on _deploy.yml it may not need robust options support. I could envision shipping something as simple as:

octopress deploy -> Octopress::Deploy::push()
octopress deploy --using git -> `Octopress::Deploy::push(method: 'git')
octopress deploy --config path_to_config_file -> Octopress::Deploy::push(config_file: path)
octopress deploy --init git -> Octopress::Deploy.init_config('git')
octopress deploy --init rsync -> Octopress::Deploy.init_config('rsync')

As it is right now, configurations for Git deployment and Rsync deployment can coexist, so you could easily switch methods with the --using flag without needing to edit the configuration file.

Running the commands:

$ octopress new post "My Title"

generates the following invalid template:

---

---
layout: post
title: My Title
date: 2014-02-24T14:42:20-08:00
categories: 

---

---

Conversely, running:

$ octopress new page about/index.markdown

generates the following invalid template:

---

---
layout: page
title: 

---

---

While testing a migration from my Octopress 2 site, I noticed an error for the "img" tag that was a default option in Octopress 2 ( http://octopress.org/docs/plugins/image-tag/ ) was missing. Should this be substituted with a jekyll plugin in my Gemfile or should we pull from https://github.com/imathis/octopress/blob/master/plugins/image_tag.rb

With some plugins missing, it also seems odd that the _plugins folder is not created by default when doing a "octopress new".

Hey @parkr! I've been hacking together my own testing framework for Octopress, Ink and various plugins. I've been copying it over to each project and trying to keep the changes in sync and that's gotten old. It's time to gemmify this thing and iterate towards greatness.

Here's what it does:

• Builds Jekyll sites and allows custom configuration for each build.
• Spins through two directories and diffs files, giving nicer output than diff -r.
• Runs a shell command and compares the output against a string.

What I wish it did.

• Allow you to run a single test without commenting out other tests.

I'm sure you'll have some great ideas for how to improve this stuff. I'll push up something you can tear apart soon.

If a subclassed command (like octopress deploy) sets the version with p.version it overrides the Octopress version (obviously). But there's no way for a subclassed command to display a version. The version flag gets swallowed up by octopress, yet the output for octopress deploy --help suggests that the version flag would work.

Does Mercenary need better support for extending commands or is there something I can do differently?

When we release 3.0, I'm concerned that people will assume it's just like 2.0 but better in some way. However, this release is very different from what Octopress has been up until this point. This will be the first part of a larger release. Octopress is shifting from being essentially a blog that you fork to a modular system of independent components. It will also be build on the latest version of Jekyll, something which Octopress is currently incompatible with due conflicts with a few plugins. Essentially, Octopress 3.0 will be better suited to Jekyll users than Octopress users, at least initially.

For those currently using Octopress, it will be a while before the new releases can compete with the features of the old version. For those who want themes and plugins, they'll have to wait for the release of octopress-ink, and themes and plugins to be built on top of it. With each release, vanilla Jekyll users will be able add the new shiny stuff to their sites.

Once Octopress is to the point where it can replace the old version, I'll need to have a plan to help people migrate. I'd love for it to be as simple as "Copy your posts into a new site, and run octopress init; octopress build, but they might be using some old liquid plugins which aren't being maintained anymore and don't work with the new version Jekyll. These users will see build errors and have to wade through their posts and pages and remove stuff that breaks things. I really hate that this is what lots of people are going to go through if they want to update their blogs.

I totally believe in what we're doing with this release, but it frustrates me to know this is what is going to happen. If this new release gets any attention at all, I'm going to be answering the "how do I migrate" question a lot, so I need to come up with a plan. I feel like that plan needs to be part of this release so here's what I want to do.

1. Get this code into imathis/octopress
2. Delete this repo
3. Move imathis/octopress to octopress/octopress
4. Rename the current master branch to 2.0-deprecated (better name?)
5. Make the branch containing this code base the new master branch.
6. rake release

Before I do that I need to have a blog post written explaining what's going on. I'm nervous about writing that post. I've sucked at managing this project and I deserve whatever criticism for the mistakes I've made. Part of me wants to delay the release of this until I can have more to show people so it will be more clear how things will work in the future. Only releasing the CLI and octopress-deploy kind of begs for a "we've waited three years for this?" response. I think Octopress-Ink will be the exciting part of this release and part of me wants to get it done before dropping the release candidate and owning the 3.0.

Anyway, that's what's swirling around in my head. Whoever reads this, feel free to advise.

This is not universally true but needs further investigation.

Steps to repeat:

1. edit _config_yml with `source: ./_source'
2. move Jekyll source into _source, leaving _config.yml, _octopress.yml, and other non-source files in the root.
3. run octopress serve --config _config.yml --octopress-config _octopress.yml

Configuration file: _config.yml
Configuration file: none
            Source: ./_source
       Destination: ./_site
      Generating...
                    done.
 Auto-regeneration: disabled. Use --watch to enable.
Configuration file: none
    Server address: http://0.0.0.0:4000/
  Server running... press ctrl-c to stop.

1. edit _config.yml with config: _config.yml
2. run octopress serve --config _config.yml --octopress-config _octopress.yml

Configuration file: config.yml
Configuration file: config.yml
            Source: ./_source
       Destination: ./_site
      Generating...
                    done.
 Auto-regeneration: disabled. Use --watch to enable.
Configuration file: config.yml
    Server address: http://0.0.0.0:4000/
  Server running... press ctrl-c to stop.

There are other indications that root as source may be hardwired or that source location is not being passed where required. I am still looking into the detail.

Thank you bundle open octopress and byebug.

octopress isolate [path] [options]

Options:

• Specifying a path will isolate all posts except for that one one.
• Passing no args will isolate only the most recent post (by date in yaml front-matter or filename).
• Passing --search flag will isolate all posts which don't match the search string.

Looking at lib/octopress/commands/serve.rb octopress will pass all commands to build first and then to serve. However, the --watch parameter will just run build and start watching there, never reaching the serve command.

Hey @parkr, Any idea what's up with this Travis failure? It works fine locally, but to get tests to pass on Travis I have to use YAML.load which, of course, will hack everyone's planet. Any ideas?

It'd be nice if we could automatically require blessed gems which extend the CLI. Like octopress/deploy for example.

Software Versions

See Gemfile and Gemfile.lock at end of post.

Steps to reproduce

• Install octopress v3.0.0.rc.22 completely from scratch:

$ gem install bundler
$ bundle install # see Gemfile at end of post

• make blank test site

$ octopress new dumy && cd dumy

• attempt to serve the site

$ octopress serve

Result

Command returns immediately, exit code 0.

Expected Result

Site is served at http://localhost:4000/.

Diagnostic Info

$ command
<output, or nothing>

$ octopress

$ octopress help

$ octopress --version
octopress 3.0.0.rc.22

# -- file: Gemfile --
source "https://rubygems.org"

gem 'octopress', '~> 3.0.0.rc.15'
gem 'compass', '~> 1.0.1'
gem 'sass-globbing', '~> 1.0.0'

# More recent versions of listen break octopress
gem 'listen', '<2.7.12'
gem 'jekyll', '~> 2.4.0'

# -- file: Gemfile.lock --
GEM
  remote: https://rubygems.org/
  specs:
    blankslate (2.1.2.4)
    celluloid (0.16.0)
      timers (~> 4.0.0)
    chunky_png (1.3.3)
    classifier-reborn (2.0.2)
      fast-stemmer (~> 1.0)
    coffee-script (2.3.0)
      coffee-script-source
      execjs
    coffee-script-source (1.8.0)
    colorator (0.1)
    compass (1.0.1)
      chunky_png (~> 1.2)
      compass-core (~> 1.0.1)
      compass-import-once (~> 1.0.5)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
      sass (>= 3.3.13, < 3.5)
    compass-core (1.0.1)
      multi_json (~> 1.0)
      sass (>= 3.3.0, < 3.5)
    compass-import-once (1.0.5)
      sass (>= 3.2, < 3.5)
    execjs (2.2.2)
    fast-stemmer (1.0.2)
    ffi (1.9.6)
    hitimes (1.2.2)
    jekyll (2.4.0)
      classifier-reborn (~> 2.0)
      colorator (~> 0.1)
      jekyll-coffeescript (~> 1.0)
      jekyll-gist (~> 1.0)
      jekyll-paginate (~> 1.0)
      jekyll-sass-converter (~> 1.0)
      jekyll-watch (~> 1.1)
      kramdown (~> 1.3)
      liquid (~> 2.6.1)
      mercenary (~> 0.3.3)
      pygments.rb (~> 0.6.0)
      redcarpet (~> 3.1)
      safe_yaml (~> 1.0)
      toml (~> 0.1.0)
    jekyll-coffeescript (1.0.1)
      coffee-script (~> 2.2)
    jekyll-gist (1.1.0)
    jekyll-paginate (1.1.0)
    jekyll-sass-converter (1.3.0)
      sass (~> 3.2)
    jekyll-watch (1.2.0)
      listen (~> 2.7)
    kramdown (1.5.0)
    liquid (2.6.1)
    listen (2.7.11)
      celluloid (>= 0.15.2)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
    mercenary (0.3.5)
    multi_json (1.10.1)
    octopress (3.0.0.rc.22)
      jekyll (~> 2.0)
      mercenary (~> 0.3.2)
      octopress-deploy
      octopress-docs
      titlecase
    octopress-deploy (1.0.0)
      colorator
      octopress-docs
    octopress-docs (0.0.11)
      jekyll (~> 2.0)
      octopress-escape-code (~> 1.0)
      octopress-hooks (~> 2.0)
    octopress-escape-code (1.0.4)
      octopress-hooks (~> 2.0)
    octopress-hooks (2.2.2)
      jekyll (~> 2.0)
    parslet (1.5.0)
      blankslate (~> 2.0)
    posix-spawn (0.3.9)
    pygments.rb (0.6.0)
      posix-spawn (~> 0.3.6)
      yajl-ruby (~> 1.1.0)
    rb-fsevent (0.9.4)
    rb-inotify (0.9.5)
      ffi (>= 0.5.0)
    redcarpet (3.2.2)
    safe_yaml (1.0.4)
    sass (3.4.9)
    sass-globbing (1.0.0)
      sass (>= 3.1)
    timers (4.0.1)
      hitimes
    titlecase (0.1.1)
    toml (0.1.2)
      parslet (~> 1.5.0)
    yajl-ruby (1.1.0)

PLATFORMS
  ruby

DEPENDENCIES
  compass (~> 1.0.1)
  jekyll (~> 2.4.0)
  listen (< 2.7.12)
  octopress (~> 3.0.0.rc.15)
  sass-globbing (~> 1.0.0)

P.S. I love what you're doing in Octopress 3 :D I'm really enjoying using v3.0.0.rc.15, and I'd love to get this issue figured out.

when performing a octopress new page test/ to generate a subdirectory in your site (e.g. http://mysite.com/test/), octopress is generating the "test" folder, but inside is a index.html file with markdown attributes. I believe it is supposed to be index.md.

i tried to create a new octopress blog, and pushing it to my github https://github.com/blazeeboy/blazeeboy.github.io using the following steps :

$ gem install octopress --pre
$ octopress new blazeboy
$ cd blazeboy
// then replaced the theme with scrubble
$ gem install octopress-deploy --pre
$ octopress deploy init git
$ octopress build
$ octopress deploy

the octopress deploy step prints the following error

Syncing _site files to [email protected]:blazeeboy/blazeeboy.github.io.git.
From github.com:blazeeboy/blazeeboy.github.io
 * branch            master     -> FETCH_HEAD
fatal: pathspec ':/' did not match any files
Everything up-to-date

so i tried the following:

$ cd .deploy
$ git add .
$ git commit -m"my message"
$ git push deploy

and it worked fine and pushed the site. https://github.com/blazeeboy/blazeeboy.github.io
now, i tried to modify a post and the following.

$ octopress build
$ octopress deploy

and it prints the same error message and doesn't commit or push anything.
my _deploy.yml file content is:

method: git                               # How do you want to deploy? git, rsync or s3.
site_dir: _site                           # Location of your your static site files.

git_url:  [email protected]:blazeeboy/blazeeboy.github.io.git

# Note on git_branch:
# If using GitHub project pages, set the branch to 'gh-pages'.
# For GitHub user/organization pages or Heroku, set the branch to 'master'.
#
git_branch: master                        # Git branch where static site files are commited


# remote_path:                            # Destination directory

and my _config.yml content:

# Site settings
title: Blaze Boy
email: [email protected]
description: "Software Engineer and Particularly a Ruby Addict"
baseurl: ''
url: "http://www.blazeboy.me"
signoff: 'E.E'

# Build settings
markdown: kramdown
permalink: /:title.html

disqus_shortname: blazeboy
facebook_appid:   1400091873588797
google_analytics: UA-53753121-1

links:
  - name:         About
    url:          /about
  - name:         Home
    url:          /
  - name:         Facebook
    url:          https://www.facebook.com/blazeeboy
    external:     true
  - name:         GitHub
    url:          https://github.com/blazeeboy
    external:     true

is there something i'm missing ?

Intro: I'm Russian and I want to write posts in Russian, but I can not use octopress 3.0 to create files from command line. Also I'm using Ruby 2.0 x64 on Windows 7 x64

I tried to set encoding of command promt to be 'windows-1251' and 65001 (utf-8) with chcp, but that did not help:

> bundle exec octopress new post "тест"
octopress 3.0.0.rc.12 | Error:  incompatible encoding regexp match (UTF-8 regexp with IBM866 string)
> chcp 1251
> bundle exec octopress new post "тест"
octopress 3.0.0.rc.12 | Error:  incompatible encoding regexp match (UTF-8 regexp with Windows-1251 string)
> chcp 65001
> bundle exec octopress new post "тест"
DL is deprecated, please use Fiddle
Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/vendor/thor/parser/arguments.rb:12:in `block in split': invalid byte sequence in UTF-8 (ArgumentError)
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/vendor/thor/parser/arguments.rb:11:in `each'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/vendor/thor/parser/arguments.rb:11:in `split'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/vendor/thor.rb:344:in `dispatch'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/vendor/thor/base.rb:440:in `start'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/cli.rb:9:in `start'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/bin/bundle:20:in `block in <top (required)>'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/lib/bundler/friendly_errors.rb:5:in `with_friendly_errors'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.6.2/bin/bundle:20:in `<top (required)>'
        from C:/Ruby200-x64/bin/bundle:23:in `load'
        from C:/Ruby200-x64/bin/bundle:23:in `<main>'

This way people can organize posts into subdirectories under _posts.

Hey All,

I'd love to see a feature that would make writing a series of blog posts much more seamless.

I totally get that if this needs to be a plugin it could, but let me describe what I think a possible experience could be like - and maybe someone could guide me to how best to implement...

I've seen some attempts already, and in fact took this one, modified a bit to give something closer to what I'd like to use - but I'm struggling to get this to render correctly in the categories feed... (I may ask for help on that specifically, depending on how this request pans out).

How I'd like to create a series.

1. In the YAML frontmatter, I'd like to say something like

---
layout:post <-- maybe series?
series_about: "Migrating from BlogSpot to OctoPress"
series_title: "Introduction"
series_id: migrate-blogspot-to-octopress

---

In this blog... I'd like to talk about...

<-- inject series tag here -->

Where the series tag looks something like

This article is Part 2 of 5 in a series about something awesome.

• Part 1 - something awesome - Introduction
• Part 2 - something awesome - (current) Step 1
• Part 3 - something awesome - Step 2
• Part 4 - something awesome - (coming soon) Step 3
• Part 5 - something awesome - (coming soon) Wrapping up

I think the specifics could be discussed - but I'm looking for something seamless - something that It makes it easy to extend/modify/re-order the series posts and when it generates - everything links up well.

Here is what I'm using currently that I can't get to render correctly in categories). But I'm doing to do it manually, until I get or build) a better work-around...

Not sure if this is possible in Jekyll - but what would be really cool, is if a series could be written as a single .markdown file and we somehow split it/tag it? (That would be a cool way to do it... in my mind :))

The backstory

I'm trying to figure out how to make Octopress as easy for people to use as possible and not have it do or assume too much about the user. Right now we have this really great documentation feature where users can run octopress docs and it will show the documentation for Octopress and all of the plugins they have. In order to do this, Octopress needs the magic of Ink and its integration with Ink plugins.

The proposal

I'd like to move the docs command to the Ink project because that's likely where it makes the most sense to live anyway. Since Octopress will mostly just be a command line utility, --help should take care of most people's documentation needs. Either that or the docs website, like we've always done.

What say you @parkr?

Hi,

Just installed a fresh copy of Octopress using

group :development do
  gem 'octopress', '~> 3.0.0.rc.16'
end

When I run the octopress docs command I get the following:

Configuration file: /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/_config.yml
Configuration file: /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/_config.yml
            Source: /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs
       Destination: /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/_site
      Generating... 
Error reading file /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/assets/docs/index.md: No such file or directory - /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/assets/docs/index.md 
Error reading file /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/README.md: No such file or directory - /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/README.md 
Error reading file /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/CHANGELOG.md: No such file or directory - /Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-docs-0.0.9/docs/Users/harry/.rvm/gems/ruby-2.0.0-p195@octopress3/gems/octopress-3.0.0.rc.16/CHANGELOG.md 
  Liquid Exception: Unknown tag 'css_asset_tag' in _layouts/default.html
octopress 3.0.0.rc.16 | Error:  Unknown tag 'css_asset_tag'

I'm trying to get the main index homepage to look like my Octopress 2 site displaying the last five articles and all of their content vs. a page that has a link to each article as seen attached.

I'm assuming it's just a setting in the _config.yml, I just can't find it. Current source is available on my octo3 repo.

Is it possible to have a post template containing containing:

permalink: /:year/:month/:day/:title

Like Jekyll does? I've tried with f.i date.year and other combinations but couldn't figure it out.