You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 15, 2020. It is now read-only.
Since moving away from Pyrofex, I've stripped out all non-static components from the www & dev sites. @dckc demonstrated simple static site migration using wget on the www site, and I've had similar success on the dev site.
These sites can be hosted as gh-pages, optionally to be placed behind a cheap CDN. Version control, CI/CD, and SSL could then be handled negatively by GitHub instead of using our current complex wiring.
Wordpress Sites
Migration of the blog site somewhat complicated because it is a "MultiSite" configuration with content that we've generated through 3rd party plugins and a deeply integrated "Divy builder framework". It is doable, but may take some time to sort out 3rd party licensing , reconfigure podcast rss builder, and re-create Divy-Builder content. The faq.rchain.coop WP site is underutilized and can be recreated elsewhere as a GitHub markdown or web page.
Consider future work of migrating blog content over to gh-pages and collapsing the blog subdomain into rchain.coop/blog) There are other free or cheap ways to host the podcast RSS feed that using the Seriously Simple Podcasting WP Plugin. Note, we've also been using the WP Yeost plugin to generate pretty badges for our Social Media posts.
Collapse dev site into www
The Subdomain vs Subdirectory issue is no longer complicated by having the www site hosted on Squarespace. With both www and dev hosted as static gh-pages it will be much easier to collapse the dev site into rchain.coop/dev.
To redirect old links, we can create additional gh-pages for www and dev that point to the new site.
Sequence
Migrate WP blog to another host
Copy www & dev into gh-pages branches
Configure www & dev rewrite repos
DNS changes
Tear down rchain/www Kubernetes and CI/CD
The text was updated successfully, but these errors were encountered:
I would like to get a better understand of how Greg wants to incorporate Dappy into the website migration. Greg will be attending the Communications working group meeting tomorrow June 9th.
ian-bloom
changed the title
Migrate Co-op Sites to gh-pages & Bluehost
Migrate Co-op Sites to gh-pages & external host
Jun 12, 2020
Why
What
How
Static Sites
Since moving away from Pyrofex, I've stripped out all non-static components from the www & dev sites. @dckc demonstrated simple static site migration using wget on the www site, and I've had similar success on the dev site.
These sites can be hosted as gh-pages, optionally to be placed behind a cheap CDN. Version control, CI/CD, and SSL could then be handled negatively by GitHub instead of using our current complex wiring.
Wordpress Sites
Migration of the blog site somewhat complicated because it is a "MultiSite" configuration with content that we've generated through 3rd party plugins and a deeply integrated "Divy builder framework". It is doable, but may take some time to sort out 3rd party licensing , reconfigure podcast rss builder, and re-create Divy-Builder content. The faq.rchain.coop WP site is underutilized and can be recreated elsewhere as a GitHub markdown or web page.
Consider future work of migrating blog content over to gh-pages and collapsing the blog subdomain into rchain.coop/blog) There are other free or cheap ways to host the podcast RSS feed that using the Seriously Simple Podcasting WP Plugin. Note, we've also been using the WP Yeost plugin to generate pretty badges for our Social Media posts.
Collapse dev site into www
The Subdomain vs Subdirectory issue is no longer complicated by having the www site hosted on Squarespace. With both www and dev hosted as static gh-pages it will be much easier to collapse the dev site into rchain.coop/dev.
To redirect old links, we can create additional gh-pages for www and dev that point to the new site.
Sequence
The text was updated successfully, but these errors were encountered: