Adding publish automation #3527
Merged
Conversation
This file contains hidden or 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
|
Hi @andrewpollack! This is awesome! Will merge this. I'm still considering this experimental for the time being, but I think it is an awesome alternative to the currently highly dependent on environment set up we have right now. Excellent work! |
nellshamrell
approved these changes
Aug 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As from README, this Dockerfile takes care of installation of
pelican,sass,juice, and other requirements.Example flow (from
publishingdirectory):make build && make generate-website && make host-contentmake build && make generate-email && make host-content, change "BLOG_DOWNLOAD" variable, and in separate terminal runmake optimize-emailMany improvements to do in future iterations...
plugins/,themes/,pelicanconf.py,requirements.txtintopublishing/