docs/quickstart: update instructions to require bundler #5168

Merged
merged 3 commits into from Aug 2, 2016

Conversation

Projects
None yet
4 participants
@parkr
Member

parkr commented Jul 30, 2016

With gem-based themes being bundled in the new site via the Gemfile, we
should ask folks to use Bundler wherever possible. This should lead to more
successful installations and getting the base site setup properly.

The only trouble this introduces is it puts a dependency on Bundler. That
said, I'm totally fine with requiring everyone use Bundler for this site.
How could we best install bundler in these instructions?

/cc @jekyll/documentation

docs/quickstart: update instructions to require bundler
With gem-based themes being bundled in the new site via the `Gemfile`, we
should ask folks to use Bundler wherever possible. This should lead to more
successful installations and getting the base site setup properly.

The only trouble this introduces is it puts a dependency on Bundler. That
said, I'm totally fine with requiring everyone use Bundler for this site.
How could we best install bundler in these instructions?

/cc @jekyll/documentation

@parkr parkr added the documentation label Jul 30, 2016

@chrisfinazzo

This comment has been minimized.

Show comment
Hide comment
@chrisfinazzo

chrisfinazzo Jul 30, 2016

Contributor

This was discussed a while back (ultimately put on hold) in #4368. For documentation, that's a starting point to build on. As far as the internals go, I recall you mentioned potentially having the ability to install specific versions similar to how the prereleases work.

With a stable v3 now available, is this a viable strategy?

Contributor

chrisfinazzo commented Jul 30, 2016

This was discussed a while back (ultimately put on hold) in #4368. For documentation, that's a starting point to build on. As far as the internals go, I recall you mentioned potentially having the ability to install specific versions similar to how the prereleases work.

With a stable v3 now available, is this a viable strategy?

@parkr

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Aug 2, 2016

Member

@jekyllbot: merge +site

Member

parkr commented Aug 2, 2016

@jekyllbot: merge +site

@jekyllbot jekyllbot merged commit 896a502 into master Aug 2, 2016

0 of 2 checks passed

jekyll/lgtm Awaiting approval from at least 2 maintainers.
continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details

@jekyllbot jekyllbot deleted the change-quickstart branch Aug 2, 2016

jekyllbot added a commit that referenced this pull request Aug 2, 2016

@parkr

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Aug 2, 2016

Member

@chrisfinazzo We could definitely encourage people to use Gemfiles from now on. It's the best way to get things working. For prereleases, we could suggest updating their gemfile to say:

gem "jekyll", "<THE-VERSION>"

etc etc etc

Member

parkr commented Aug 2, 2016

@chrisfinazzo We could definitely encourage people to use Gemfiles from now on. It's the best way to get things working. For prereleases, we could suggest updating their gemfile to say:

gem "jekyll", "<THE-VERSION>"

etc etc etc

@chrisfinazzo chrisfinazzo referenced this pull request Aug 3, 2016

Closed

Updates for Bundler #5198

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment