-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Replace Website with github pages #967
Comments
I replaced the master branch on https://github.com/deegree/deegree.github.io with the squashed version of the prepared jekyll based one. This version is now available at http://deegree.github.io/. I've also prepared the use of www.deegree.org / deegree.org via the Github page settings, so we can trigger the DNS changes tomorrow if there are no new change requests to the page in the TMC meeting tomorrow. |
To test the website, you must access it via http until the DNS is updated.
|
The required changes would be:
|
Issue for OSGeo SAC created https://trac.osgeo.org/osgeo/ticket/2272 |
The DNS change took place on the weekend, so the website address had to be changed in the configuration to avoid HTTPS warnings. This was done in commit deegree/deegree.github.io@4b76d0f. |
I reopended the sac issue at https://trac.osgeo.org/osgeo/ticket/2272#comment:5 as it looks like other entries have been changed. |
Due to the dns problems we have decided to continue redirecting from deegree. org to www.deegree.org via plaza. (https://trac.osgeo.org/osgeo/ticket/2272#comment:12) I also disabled the jommla site on plaza. |
In today's TMC Metting from 24.05. we agreed to continue the still open items as separate issues, accordingly this issue will be closed. |
The following activities have to be done to replace the old website with github pages:
(Aggreated from the TMC meeting https://github.com/deegree/deegree3/wiki/tmc-meeting-minutes-20190329)
content releated tasks
including the backend functions)administrative tasks
post migration tasks
After processing this issue, the following issues are no longer relevant:
The previous evaluation was done in Issue #906
The text was updated successfully, but these errors were encountered: