Fixes #23 Deploy site for each git branch #170
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
|
Probably found a bug. Will notify you after the fix. |
visortelle
force-pushed
the
gh23-deployment
branch
from
78f1799 to
2ed5891
Compare
|
Now it should work. |
visortelle
force-pushed
the
gh23-deployment
branch
from
2ed5891 to
e685013
Compare
visortelle
force-pushed
the
gh23-deployment
branch
from
30a0666 to
2f9fa45
Compare
|
Implemented deployment deletion after branch deletion. |
|
For development branches added a meta tag to block search bots indexing. https://developers.google.com/search/docs/advanced/crawling/block-indexing Done by monkey-patching html files after each build: replace |
visortelle
changed the title
visortelle
changed the title
Merged
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.
Hello.
I implemented per-branch deployment for the site.
Demo
Deployments List
If you'll make your own experiments with the PR, be patient with GitHub pages. Update sometimes took up to 5 minutes.
How it works
The
hakyllbranch will be available at<domain_name>/.Other branches are available at
<domain_name>/branches/<branch_name>.It doesn't support automated PRs build. I described manual steps for PR creators on how to create a demo deployment here: https://github.com/visortelle/haskellfoundation.github.io#prs-deployment
Alternative
The approach with GitHub pages implemented here is the simplest way to achieve the goal that comes to my mind. An alternative approach would require extra infra resources like VM access or S3 bucket, plus automation to dynamically create and remove DNS records.
Or much simpler - switch from gh-pages to Vercel or similar hosting that supports feature branch deployments out of the box. Unfortunately, Vercel doesn't support Haskell out of the box, therefore it’s not an option if usage Hakyll is a matter of principle.
If the PR is OK for you.
There are simple extra actions you should do.
/docsdirectory.gh-pagesbranch from here https://github.com/visortelle/haskellfoundation.github.io/tree/gh-pages togh-pagesbranch in this repo.I hope that's it.