Jekyll is not serving when I use the --drafts flag. I get the following error:
[2017-02-11 15:49:48] ERROR `/files/' not found
It works fine when I don't call --drafts.
So, this works:
jekyll serve --watch --baseurl ""
But this doesn't:
jekyll serve --watch --baseurl --drafts ""
I have also tried removing all else, so it is just:
jekyll serve --drafts
I have a draft post in my _drafts directory, which is marked with draft: true (I have also tried published: false and leaving that out entirely.
The contents of _config.yml are:
baseurl: /blog
exclude: ['README.md']
permalink: pretty
# Conversion
markdown: kramdown
highlighter: rouge
# Markdown Processors
kramdown:
input: GFM
auto_ids: true
syntax_highlighter: rouge
It might be worth noting that syntax highlighting isn't working either, so the errors may (or may not) be related.
Related
Pretty permalinks are working file locally but not once deployed to GitHub Pages. Puzzled what might be a reason. Pages can be still accessed via .html.
_config.yml
title: Project Name
baseurl: /project-name
url: "http://organization-name.github.io"
google_analytics: # set tracking
gems:
- jekyll-redirect-from
exclude:
- Gemfile
- Gemfile.lock
permalinks: pretty
markdown: kramdown
Gemfile
source "https://rubygems.org"
ruby RUBY_VERSION
gem "github-pages", group: :jekyll_plugins
group :jekyll_plugins do
end
The right syntax is permalink: pretty : singular.
So I solved this issue by adding permalink explicitly to page meta. E.g.
permalink: /about/
Strange that it is not required locally.
You have to modify your _config.yml
defaults:
-
scope:
path: ""
type: "pages"
values:
permalink: "/:basename/"
You may want to tweak this example.
For example, if you want to keep your folder structure in your permalinks, you could have:
defaults:
-
scope:
path: ""
type: "pages"
values:
permalink: "/:path/:basename/"
Note: "pretty" is "/:path/:basename/"
I'm trying to get some very simple pages to render properly with Jekyll using kramdown to process markdown and rouge for syntax highlighting. Kramdown appears to not interpret triple-backticks, however, even in GFM mode.
I believe I've followed the instructions to the letter, and things work out fine when pushed to github pages, but my local setup just ignores the backticks.
If it's any help, this has been observed on OS X with Jekyll 3.1.1. The command line used to invoke jekyll is jekyll serve --config "_config.yml".
I've narrowed the problem to the following minimal test:
_config.yml
markdown: kramdown
highlighter: rouge
kramdown:
input: GFM
index.md
---
layout: default
---
```scala
def test(i: Int): Unit = {
println(i)
}
```
layout/default.html
<!doctype html>
<html>
<body>{{ content }}</body>
</html>
Resulting index.html
<!doctype html>
<html>
<body><p>```scala
def test(i: Int): Unit = {
println(i)
}</p>
<p>```</p>
</body>
</html>
I suggest you to do like this. I tested your code block whit the following configuration and it worked fine:
config.yml :
highlighter: rouge
markdown: kramdown
kramdown:
input: GFM
Then, to your file index.md:
```scala
def test(i: Int): Unit = {
println(i)
}
```
Note: I've noticed that there was a space before ```scala and it shouldn't be there.
Then, run jekyll serve with bundler:
Open your terminal and:
Install bundler:
gem install bundler
Update all your gems (if you want):
bundle update
Add a Gemfile (don't add any file extension) to your site root and paste the code below into it. This is GitHub Pages recommended method.
source 'https://rubygems.org'
gem 'github-pages'
Go to your project root folder (on the terminal) and run:
bundle install (this will make sure you have all required gems and their dependencies installed locally). A Gemfile.lock will be generated for you at your site root. Leave it there.
Run bundle exec jekyll serve --watch to view your site locally at http://localhost:4000
Done!
Let me know if this works for you, yeah?
My current _config.yml file looks like this:
#Site settings
...
baseurl: "" # the subpath of your site, e.g. /blog/
url: "http://10.0.1.9:3000" # the base hostname & protocol for your site
...
# Build settings
markdown: kramdown
safe: true
lsi: false
highlighter: true
keep_files: [public]
exclude: [src, lib, node_modules, bower.json, Gemfile, gulpfile.js, package.json, README.md]
I've got my url currently set to my local server, where I serve my Jekyll site for local development.
When building for production however, I have to keep manually changing this url to the url of my remote server before running jekyll build. Is there a way I can pass my remote url alongside the jekyll build command to build a site with the correct remote paths?
Something like so:
jekyll build --url mysite.com
Any help is appreciated with this. Thanks in advance!
Put your production url in _config.yml eg: url: toto.com.
Create a _config_dev.yml that will be used to override values in development.
In you case
url: "http://10.0.1.9:3000"
Development build is launched with :
jekyll build --config _config.yml,_config_dev.yml
Values in the last config file in the command will override those in first file.
and production build with jekyll build.
See Jekyll documentation http://jekyllrb.com/docs/configuration/#build-command-options configuration paragraphe.
I am trying to jekyll serve a website that was created with a previous version of jekyll.
I had to update my _config.yml file from this:
#Build settings
markdown: rdiscount
pygments: true
paginate: 100
permalink: pretty
To this:
#Build settings
markdown: rdiscount
highlighter: pygments
paginate: 100
permalink: pretty
This should be OK but I get the following error when I try to serve the application.
jekyll 2.0.3 Error: undefined method `pygments_prefix' for #<Jekyll::Converters::Identity>`
Any help on that? Thank you
According to my experience with the very same problem, this function and its `suffix' sibling have been renamed to highlighter_prefix and highlighter_suffix in Jekyll 2.0.3.
This is probably caused by one of your plugins, grep them out and replace them and things might just work.
Good luck!
I had a blog running at morenoh149.github.io I attempted to add yeoman to my workflow using jekyllrb generator. I followed the instructions by creating a new yeoman project, and copying over all the generated files and structure to my blog. But now github pages isn't picking up the blog. https://github.com/morenoh149/morenoh149.github.io
Anyone know how github pages works? the docs are sparse.
I changed the source in my yml file to app/ as well. So now when I run jekyll locally it works. But when I push to github pages it's not.
_config.yml
# Jekyll configuration precedence:
# 1. Gruntfile task
# 2. config.build.yml
# 3. config.yml
name: morenoh149.blog.yeoman
url: morenoh149.github.io
description: Harry Moreno has a blog
author:
name: Harry Moreno
email: morenoh149#gmail.com
# Grunt handles images and assets.
exclude: ['img', 'css', 'js', 'fonts',
'**.png', '**.jpg', '**.jpeg', '**.gif', '**.webp', '**.svg', '**.ico']
include: ['.htaccess']
source: app
# _config.build.yml sets future and show_drafts to false on `grunt build`
future: true
show_drafts: true
# Markdown library
markdown: redcarpet
# extensions: ['fenced_code_blocks', 'smart']
pygments: true
It looks like GitHub Pages is serving files from your site (for instance, http://morenoh149.github.io/app/ is an html file with a single paragraph element) but it's not serving them properly with all the Jekyll magic.
It turns out that GitHub Pages will override the source setting in the config file. This means that while you've specified source: app, it's looking at your top-level directory for content.
The solution is to move the contents of your app directory into your top-level directory.