Adds automatic build via Travis and Surge.sh - #19
Open
kennethormandy wants to merge 4 commits into
Open
Conversation
Author
|
Hey, just checking in on this. The cookbook helped me a lot recently—I’d be happy to help contribute back by getting the auto-building and deploying for the site working if you’re still interested. |
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
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.
This PR isn’t ready to merge as-is, but I do have the first option I described here #17 (comment) working on my fork.
opentypecookbook-example.kennethormandy.com/ is automatically compiled and deployed when I push to that repository. This also means that if people open PRs for typos, you can merge them and the site will automatically be rebuilt and published too.
The site would be hosted on Surge.sh (full discolsure, it’s where I used to work and I’m still involved) which I find it a lot easier than the GitHub Pages approach to deployment. Most of this is still usable even if you decide you want it on GitHub Pages instead, though, only the
deployscript in the.travis.ymlfile would change.If you want to set this up on the main repo, some things that would need to happen:
predeployscript I added, so my copy doesn’t show up in search resultsI realise that’s kind of a long list, but most of those things I couldn’t take care of because they require credentials. If you did want help on that part too and don’t mind giving me some level of access to the repository, I could do everything other than the DNS settings. Let me know what you think.