-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jekyll-seo-tag does not seem to be supported #16
Comments
It should be installed already as a dependency of the gems:
- jekyll-seo-tag |
It is enabled 😕 |
Any ideas? |
@adius could you supply your |
@siliconmeadow Yes, but nothing interesting to see there <!doctype html>
<html>
<head>
<meta charset=utf-8 />
<meta name=viewport content="width=device-width, initial-scale=1">
<link rel=stylesheet media=all href=/css/screen.css>
<link rel="shortcut icon" href=/img/favicon.png>
<link
rel=stylesheet
href=//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css>
<link
href=/atom.xml
rel=alternate
title="Adrian Sieber"
type=application/atom+xml>
{% seo %}
</head>
<body>
… |
I've never used this gem before, but looking at http://jekyll.github.io/jekyll-seo-tag/installation/ , it says that you need to add this prior to the
I don't know if that would help? |
My mistake - just prior to the closing |
I'm looking through the issues, and it looks like others have an What I'm wondering is whether the problem with the jekyll-seo-tag gem in your circumstance is not that the gem isn't installed in the docker image, but that it's not correctly invoked in your templates? |
No, I don't think so. I've been using the plugin before with https://github.com/github/pages-gem and it worked like a charm, but I'm sick of dealing with ruby & bundler issues and that's why I wanted to use a docker based solution... |
Yeah, ruby and bundler is such a mess... 😠 |
Long shot @adius but you might try stopping the container, deleting your Gemfile.lock and bringing docker up again to force bundler to start over. I had some weirdness with jekyll gems that went away when I blew the lock file away. |
Thanks a lot @smeyfroi. This wasn't exactly the problem, but it led me on the right way. The How should this be fixed? A warning if the Gemfile is missing? Or automatically adding one? |
@adius Nice! It is confusing, and not really explained very well in the jekyll docs (that I could find anyway). So perhaps document that both a Gemfile and the _config.yml Also maybe worth explaining that bundler is invoked during container startup: I found myself reading the Dockerfile to understand what was going on. And the problem I had was with gem dependency conflicts that went away when I deleted the Gemfile.lock. So perhaps that's worth noting in the docs as well, as a troubleshooting thing? |
Great writeput @smeyfroi 👍 We should definitely add this to the project README I think. |
I can take a look and raise a PR over the next couple days. |
The text was updated successfully, but these errors were encountered: