Skip to content
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

WIP: Do not advise users to install Jekyll outside of Bundler #6927

Merged
merged 2 commits into from Apr 30, 2018
Merged

WIP: Do not advise users to install Jekyll outside of Bundler #6927

merged 2 commits into from Apr 30, 2018

Conversation

chrisfinazzo
Copy link
Contributor

This probably should have been in #6881. It seems reasonable to me that Jekyll should be under Bundler's purview. This is consistent w/ instructions here and is useful if you don't run jekyll new (which calls bundle install internally). The wording is a bit repetitive, so that might need to be tweaked.

@pathawks
Copy link
Member

The purpose of gem install jekyll is so users can run jekyll new MySite anywhere and get a new site scaffolding.

This does mean that there may be a difference between the system Jekyll and the Bundler Jekyll. If this issue needs fixing, it might require a more wholistic view of how we expect users to install/run Jekyll then this PR currently provides.

@chrisfinazzo
Copy link
Contributor Author

This does mean that there may be a difference between the system Jekyll and the Bundler Jekyll. If this issue needs fixing, it might require a more wholistic view of how we expect users to install/run Jekyll then this PR currently provides.

I think this is the key here. No question, this is incomplete at the moment. Over time, the trend in the documentation has become more "Bundler-oriented" and it is expected to be part of your gem management (on some level) with regard to Jekyll projects. #4368 was an early attempt at this, but I think things have matured to the point where it warrants consideration again.

Obviously, we shouldn't dictate environments if at all possible, but not doing this at some point just sounds like a compatibility headache that users shouldn't have to worry about. It doesn't solve the entire problem (which itself is nigh-impossible because software is hard) but it does make the management of these things a bit easier by removing some complexity from the equation.

@chrisfinazzo chrisfinazzo changed the title Add Jekyll to the Gemfile Discussion: Add Jekyll to the Gemfile Apr 16, 2018
@pathawks
Copy link
Member

but I think things have matured to the point where it warrants consideration again.

Agreed.

/cc: @jekyll/documentation

@pathawks pathawks changed the title Discussion: Add Jekyll to the Gemfile WIP: Discussion: Add Jekyll to the Gemfile Apr 16, 2018
@pathawks pathawks requested a review from a team April 16, 2018 03:09
@DirtyF
Copy link
Member

DirtyF commented Apr 16, 2018

We should link to https://jekyllrb.com/tutorials/using-jekyll-with-bundler/ in the About Bundler section, and even merge the whole so that we keep it a quickstart guide.

@pathawks pathawks changed the title WIP: Discussion: Add Jekyll to the Gemfile WIP: Do not advise users to install Jekyll outside of Bundler Apr 16, 2018
docs/index.html Outdated
<p class="line">
<span class="path">~</span>
<span class="prompt">$</span>
<span class="command">bundle add jekyll && bundle install</span>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use &amp; instead here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@crispgm, I used it because it is the convention in Bash to indicate “Run this command, now run that command” after the first one completes. I don’t know enough with regard to character encodings to say if this would cause Unicode issues and not display correctly in some browsers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrisfinazzo there is no issues with &&, I mean we should use &amp; to show a & in HTML.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried it out just to be sure, looks the same, so I'm 👍🏼 on this.

gem install bundler

# Add Jekyll to your Gemfile and install its dependencies
bundle add jekyll && bundle install
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One would need to run bundle init or be certain they have a valid Gemfile before they can run bundle add

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m not sure where this Gemfile would exist. Some directory that is a parent of all of a users Jekyll sites?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why the docs currently recommend the jekyll new approach after gem install jekyll. Its a lot simpler..

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered whether or not to expicitly mention bundle init here, as it is already described in some detail on the tutorial that we will be linking. Is that just repeating ourselves for no reason?

screen shot 2018-04-16 at 3 40 17 pm

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bundle add jekyll is detailed in that tutorial as well.. So, your concern is actually moot since bundle init is a necessary step for bundle add jekyll to run successfully..

@@ -26,7 +29,7 @@ If you encounter any unexpected errors during the above, please refer to the [tr

## About Bundler

`gem install jekyll bundler` installs the [jekyll](https://rubygems.org/gems/jekyll/) and [bundler](https://rubygems.org/gems/bundler) gems through [RubyGems](https://rubygems.org/). You need only to install the gems one time &mdash; not every time you create a new Jekyll project. Here are some additional details:
`gem install bundler` installs the [bundler](https://rubygems.org/gems/bundler) gem through [RubyGems](https://rubygems.org/). You need only to install it once &mdash; not every time you create a new Jekyll project. Here are some additional details:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may consider rewording this sentence to:

- You need only to install it once &mdash; not every time you create a new Jekyll project.
+ You only need to install it once &mdash; not every time you create a new Jekyll project.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, will update.

Might be a little while as I just finished restoring from a Time Machine backup.

Tl;dr, 10.13.4 "delta" Installer is 💩 .

smash-computer

@pathawks pathawks requested a review from a team April 30, 2018 14:54
@DirtyF
Copy link
Member

DirtyF commented Apr 30, 2018

@jekyllbot: merge +docs

@jekyllbot jekyllbot merged commit 3e32d12 into jekyll:master Apr 30, 2018
jekyllbot added a commit that referenced this pull request Apr 30, 2018
@chrisfinazzo chrisfinazzo deleted the bundle-add branch April 30, 2018 16:13
<p class="line">
<span class="path">~</span>
<span class="prompt">$</span>
<span class="command">bundle add jekyll &amp; &amp; bundle install</span>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm...not that clever. Sorry about this - as written, it's a syntax error. Fix is in #6969.

@jekyll jekyll locked and limited conversation to collaborators Jul 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants