Add deploy scripts for namecoin.org website. #202
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
|
@josephbisch any chance you could review this? |
|
@midnightmagic Any chance you could review this? |
|
@cassiniNMC any chance you could review this? |
|
@domob1812 Any chance you could review this? |
|
@brandonrobertz any chance you could review this? |
|
@hlandau any chance you could review this? |
|
@jonasbits Any chance you could review this? |
|
These are big and difficult to audit, and might make more sense as a gist. Any particular reason to do all of this stuff, and not just clone into a temp dir, build, and rsync over? |
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.
@cassiniNMC has expressed an interest in being able to deploy from Jekyll to the Namecoin website. These are the scripts I routinely use to deploy. They're slightly Qubes-specific (I run Jekyll in a dedicated offline VM), but it should be easy to adapt them to more standard GNU/Linux and macOS systems.
Note that the scripts aren't marked as executable (I figured making them executable might pose a security risk to the server), so you need to run them as
bash deploy_public.shinstead of./deploy_public.sh.