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

Uses the jekyll _config.yml file to determine the webroot path #90

Closed

Conversation

arthur24b6
Copy link

Currently jekyll-auth assumes that the webroot is always _site. If the destination is specified in _config.yml it should be respected.

Note: this is revised from my original PR due to some failures of my coffee this morning.

rescue
{}
end
end
Copy link
Owner

Choose a reason for hiding this comment

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

This can be simplified to:

def self.jekyll_config
  @config ||= YAML.safe_load_file(config_file)
rescue
  {}
end

Copy link
Owner

Choose a reason for hiding this comment

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

Actually, on second thought, I'm not sure that we should rescue. If the Config has an error, we should fail loudly.

@stale stale bot added the wontfix label Aug 29, 2017
@stale
Copy link

stale bot commented Aug 29, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@benbalter
Copy link
Owner

@arthur24b6 thanks for this. Any interest in still seeing this merged?

@stale stale bot removed the wontfix label Aug 29, 2017
@benbalter benbalter mentioned this pull request Sep 26, 2017
@stale
Copy link

stale bot commented Oct 28, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Dec 27, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 27, 2017
@shreve
Copy link
Contributor

shreve commented Dec 29, 2017

I'm interested to see this merged. What information is still needed?

@stale stale bot removed the wontfix label Dec 29, 2017
@benbalter
Copy link
Owner

I'm interested to see this merged. What information is still needed?

It looks like there are some merge conflicts on master. If you submit a new PR that resolves those commits, and tests pass, glad to get this merged.

@stale
Copy link

stale bot commented Mar 3, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 3, 2018
@stale stale bot closed this Mar 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants