<commit_before># BrewLog

## Background
[Jekyll](https://github.com/jekyll/jekyll) is a static site generator that's perfect for GitHub hosted blogs.

[Jekyll-now](https://github.com/barryclark/jekyll-now) makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.

[BrewLog](https://github.com/benjholla/BrewLog) extends jekyll-now to create a version controlled homebrewing log/website.

- You don't need to touch the command line
- You don't need to install/configure ruby, rvm/rbenv, ruby gems :relaxed:
- You don't need to install runtime dependencies like markdown processors, Pygments, etc
- If you're on Windows, this will make setting up Jekyll a lot easier
- It's easy to try out, you can just delete your forked repository if you don't like it

In a few minutes you'll be set up with a minimal, responsive homebrew log giving you more time to spend on homebrewing or coding or whatever.

If your not sold already, checkout a **[Live Demo](https://benjholla.github.io/BrewLog/)**.

## Quick Start
BrewLog can be deployed as a Github Project page (`your_github_username_or_organization_name.github.io/BrewLog`) or as your User or Organization page (`your_github_username_or_organization_name.github.io`).  To deploy as a Project page follow Step 1A.  To deploy as a User or Organization page follow step 1B.

### Step 0)

Fork this repository to your Github User or Organization account.

### Step 1A) Deploy BrewLog as a Project Page

First, if you don't like the name `BrewLog` as your base URL then rename your repository to something you see more fitting.

Next delete the `gh-pages` branch.

Enter `BrewLog` (or whatever you entered for the base URL) in the `baseurl` field of the _config.yml file.

Once you've committed the change to _config.yml, create the `gh-pages` branch again fresh off of the latest master!

Your Jekyll based homebrew log should be viewable now at `your_github_username_or_organization_name.github.io/BrewLog` (or whatever base URL you changed your repo name to be in place of `BrewLog`.

### Step 1B) Deploy BrewLog as a User or Organization Page

Rename the repository to `your_github_username_or_organization_name.github.io`.

Your Jekyll based homebrew log should be viewable immediately at `your_github_username_or_organization_name.github.io` (if it's not, you can often force it to build by completing step 2.<commit_msg>added forward slash<commit_after># BrewLog

## Background
[Jekyll](https://github.com/jekyll/jekyll) is a static site generator that's perfect for GitHub hosted blogs.

[Jekyll-now](https://github.com/barryclark/jekyll-now) makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.

[BrewLog](https://github.com/benjholla/BrewLog) extends jekyll-now to create a version controlled homebrewing log/website.

- You don't need to touch the command line
- You don't need to install/configure ruby, rvm/rbenv, ruby gems :relaxed:
- You don't need to install runtime dependencies like markdown processors, Pygments, etc
- If you're on Windows, this will make setting up Jekyll a lot easier
- It's easy to try out, you can just delete your forked repository if you don't like it

In a few minutes you'll be set up with a minimal, responsive homebrew log giving you more time to spend on homebrewing or coding or whatever.

If your not sold already, checkout a **[Live Demo](https://benjholla.github.io/BrewLog/)**.

## Quick Start
BrewLog can be deployed as a Github Project page (`your_github_username_or_organization_name.github.io/BrewLog`) or as your User or Organization page (`your_github_username_or_organization_name.github.io`).  To deploy as a Project page follow Step 1A.  To deploy as a User or Organization page follow step 1B.

### Step 0)

Fork this repository to your Github User or Organization account.

### Step 1A) Deploy BrewLog as a Project Page

First, if you don't like the name `BrewLog` as your base URL then rename your repository to something you see more fitting.

Next delete the `gh-pages` branch.

Enter `"/BrewLog"` (or whatever you entered for the base URL) in the `baseurl` field of the _config.yml file.

Once you've committed the change to _config.yml, create the `gh-pages` branch again fresh off of the latest master!

Your Jekyll based homebrew log should be viewable now at `your_github_username_or_organization_name.github.io/BrewLog` (or whatever base URL you changed your repo name to be in place of `BrewLog`.

### Step 1B) Deploy BrewLog as a User or Organization Page

Rename the repository to `your_github_username_or_organization_name.github.io`.

Your Jekyll based homebrew log should be viewable immediately at `your_github_username_or_organization_name.github.io` (if it's not, you can often force it to build by completing step 2.
{'fraction_non_alphanumeric': 0.06849885488236519, 'fraction_numerical': 0.0024984384759525295, 'mean_word_length': 4.705463182897862, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7601416', 'n_tokens_mistral': 1441, 'n_tokens_neox': 1352, 'n_words': 655}