-
Notifications
You must be signed in to change notification settings - Fork 665
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
Migrate hosting to Netlify #854
Comments
I started writing the redirect rules, and they seem to be working okay. If you visit http://devopsdays-legacy.netlify.com/events/2009-ghent/ and click on One thing I noticed is that the event pages have the blue nav bar at the bottom, which lists other events, and it's of course going to keep being out of date (since we don't keep building it): I'm thinking we should just whack the bottom blue nav from |
Yes. I created that particular attempt at nav in mid-2015 or so. It's not necessary to keep it. |
I've removed the blue bar from legacy :) Associated commits: |
I'm all about the magic 👍 |
DNS has been updated. I do not want to remove the legacy code for a few days while DNS updates (DNS has to be updated for the legacy redirects to function) |
This PR is in place to remove the static files for legacy: |
The wercker build application has been removed. We just need to removew the |
The repo has been rewritten with |
And with that...this is resolved! |
This is to track the migration of web hosting from GH Pages to Netlify.
The work needed is as follows:
devopsdays/devopsdays-legacy
GitHub repo for the static content of the older webby-driven stuff.legacy.devopsdays.org
Netlify build/hosting for older, webby-driven content (from thedevopsdays/devopsdays-legacy
repo)www.devopsdays.org/*
for all site-level links onlegacy.devopsdays.org
legacy.devopsdays.org
in Cloudflare, pointing to appropriate cname for Netlify.devopsdays-web
for the older events, redirecting tolegacy.devopsdays.org
devopsdays.org
andwww.devopsdays.org
/static/events
for the legacy sitesThe text was updated successfully, but these errors were encountered: