Skip to content

Use Lanyon instead of rack-jekyll #1212

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

Merged
merged 2 commits into from
Nov 14, 2015
Merged

Use Lanyon instead of rack-jekyll #1212

merged 2 commits into from
Nov 14, 2015

Conversation

stomar
Copy link
Contributor

@stomar stomar commented Nov 14, 2015

@hsbt

I switched from rack-jekyll to the (new) lanyon gem.

rack-jekyll is essentially unmaintained and until a couple of weeks ago was a real mess: buggy, no tests at all, unused garbage code... After providing lots of tests and essentially nearly rewriting the whole thing, I decided to start fresh with a new gem, "Lanyon". It should work work just as good, and drops some functionality that we do not need (namely: no auto regeneration).

Note: lanyon 0.2.0 is the first gem release; versions 0.1.x belong to an unrelated yanked gem.

stomar added a commit that referenced this pull request Nov 14, 2015
Use Lanyon instead of rack-jekyll
@stomar stomar merged commit 180d1d5 into ruby:master Nov 14, 2015
@stomar
Copy link
Contributor Author

stomar commented Nov 14, 2015

After CI checks passed and staging looked fine it's now in production.

Please report any problems.

@hsbt
Copy link
Member

hsbt commented Nov 14, 2015

@stomar Great. I have bit of worry for maintenance status of rack-jekyll. I'm ok to replace with https://github.com/stomar/lanyon/ .

@stomar
Copy link
Contributor Author

stomar commented Nov 14, 2015

I have bit of worry for maintenance status of rack-jekyll

Yep, me too. It was really an effort to get gem updates pushed to RubyGems.org.

@JuanitoFatas
Copy link
Member

Nice work! 👏

@stomar stomar deleted the use-lanyon branch November 14, 2015 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants