Migrate hosting to Firebase Static Hosting #17
Merged
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
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.
I'm going to merge this now; making this a pull request for clarity for the future.
For "simplicity" (nothing is ever exactly simple), I've decided to migrate the hosting portion of this site to Google Firebase Static Hosting. I've updated README accordingly.
Action required: @shaunagm , you specifically need to click a link that Google sent you so you can be added to the opensource-events-com Firebase project. Once you are in it, I consider you the owner; feel free to ask me for advice, but it's yours, change the site if you want, etc. I'll aim to keep it online, which should happen automatically even if I do nothing; I'll also keep renewing the domain for five years or so, and then we can think again.
My request is that you try doing a deploy on your own, and try it, and make sure that you understand what I've done, and make sure the docs are something you'll understand if you ever need to fix a typo or something later.
For what it's worth, I picked Google Firebase Static Hosting because:
It's easy to set up HTTPS.
If we keep the site using Sphinx, then Sphinx has a concept of the site's source code (which is in GitHub at https://github.com/openhatch/in-person-event-handbook ) as well as concept of the built site (which is the HTML that people see). I think it's straightforward to use GitHub for only one of these (source code), and to use a different thing for the site hosting, since otherwise it's too easy to get confused and think that the GitHub source code is also the place that stores the live site.
Right now, due to the way I migrated this site, there is another GitHub repository that contains the built site, and this is confusing IMHO: https://github.com/openhatch/opensource-events.com . I'll probably delete that once the site works properly in Firebase.
Firebase Static Hosting is free of charge (up to 10GB/mo of transfer, which seems fine to me), so it's equally good to GitHub Pages in that regard.
In the process, I have temporarily replaced the site with a HTTPS error page; this should self-heal within approx 24 hours.
I'm writing this in a hurry to get it done, so if my tone seems off, please know that I am writing this in the interest of being informative; if some of it is redundant with things you already know, no condescension meant.
You can add this info to the README if you want!
Let me know when you try the deploy.sh file!
Best!,
Asheesh.