-
-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move API from AWS to GitHub Pages #397
Comments
@MikeRalphson What do you think? |
Sounds good. Will have a go at deploying to the |
FYI - I usually have an easier time deploying to the |
Thanks @bobby-brennan but in this case I think having the deployed APIs also visible in a |
@IvanGoncharov |
@MikeRalphson Without |
@IvanGoncharov I wasn't querying the need for |
Directory structure of |
FYI - I think you'll need a proxy like CloudFlare or AWS CloudFront to maintain support for HTTPS |
@bbrennan isn't that exactly the issue addressed by the blog posting Ivan linked to initially (https://blog.github.com/2018-05-01-github-pages-custom-domains-https/)? One person who needed www. support as well should not block us. |
Oh nice! I missed that, thanks
…On Wed, May 9, 2018, 1:58 AM Mike Ralphson ***@***.***> wrote:
@bbrennan <https://github.com/bbrennan> isn't that exactly the issue
addressed by the blog posting Ivan linked to initially (
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/)?
One person who needed www. support as well should not block us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#397 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHQmRfR9cQx3jt6Qw9bCd5R5lCarLxrfks5twoWUgaJpZM4Tv1HX>
.
|
Migration completed a few weeks ago ⏳ |
GitHub now supports custom domains so we can move
api.apis.guru
to gh_pages branch of this repo:https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
Probably makes sense to deploy using Travis:
https://docs.travis-ci.com/user/deployment/pages/
The text was updated successfully, but these errors were encountered: