This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
Various Jekyll/build improvements #2194
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Compress file AOD. - Let the server only use static files. - Don't add github-pages to jekyll-plugins group, due to the fact github-pages will behave differently when enabling production ENV. - Adds an extra 10s for the `host` to use `./buid.sh` due to compressing all files. - Resolves #2186
Locking to 2.0.1 was a necessary workaround for a Netlify bug which has finally been resolved.
|
Blocked by netlify/build-image#517 |
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
.ruby-version, to ensure developers are using identical software to build machines and Netlify.github-pagesgem tojekyllgem.ruby-sass, which is EOL.build.shto.buildrc.sourced within the build scripts on production servers. Commands should be assumed to be running in the main directory ($HOME/privacytools.io) directly following a fresh pull from GitHub.