dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: init project (#8450) 

Merge pull request 8450
This commit is contained in:
Rachel Cheyfitz - Owner 2020-10-29 19:03:46 +02:00 committed by GitHub
parent 25ccfd5b49
commit ebac932f10
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/_docs/step-by-step/10-deployment.md
View File

@ -11,18 +11,27 @@ It's good practice to have a [Gemfile](/docs/ruby-101/#gemfile) for your site.
This ensures the version of Jekyll and other gems remains consistent across This ensures the version of Jekyll and other gems remains consistent across
different environments. different environments.
Create `Gemfile` in the root with the following: Create a `Gemfile` in the root.
The file should be called 'Gemfile' and should *not* have any extension.
You can create a Gemfile with bundler and then add the `jekyll` gem:
```ruby ```sh
source 'https://rubygems.org' bundle init
bundle add jekyll
gem 'jekyll'
``` ```
Then run `bundle install` in your terminal. This installs the gems and Your file should look something like:
creates `Gemfile.lock` which locks the current gem versions for a future
`bundle install`. If you ever want to update your gem versions you can run ```ruby
`bundle update`. # frozen_string_literal: true
source "https://rubygems.org"
gem "jekyll"
```
bundler installs the gems and creates a `Gemfile.lock` which locks the current
gem versions for a future `bundle install`. If you ever want to update your gem
versions you can run `bundle update`.
When using a `Gemfile`, you'll run commands like `jekyll serve` with When using a `Gemfile`, you'll run commands like `jekyll serve` with
`bundle exec` prefixed. So the full command is: `bundle exec` prefixed. So the full command is: