[JDO-788] Decide what to do with GitHub pages setup

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JDO 3.1
• Fix Version/s: JDO 3.2
• Component/s: site and infrastructure
• Assignee: Unassigned
• Reporter: Tobias Bouschen
• Created: 28/Jan/21 20:58
• Updated: 17/Feb/22 19:54
• Resolved: 13/Feb/21 12:56

Description

The JDO website is currently also being hosted as GitHub pages under https://apache.github.io/db-jdo-site/. The hosted resources are located in the 'docs' directory on the master branch.

With the move to publishing the website from the separate 'publish' branch, this GitHub pages setup will no longer work. After the cleanup PR #15 is merged, the GitHub pages URL will only display a 404 error.

A decision has to be made on how to proceed with the GitHub pages setup. Either it should be disabled or we should try to adapt the setup on the 'publish' branch to be compatible with GitHub pages.

To host GitHub pages from the 'publish' branch, the resources would have to be located in the root directory or in the 'docs' directory. For the Apache hosting setup, the resources are required to be located in the 'content' directory.

From my tests, including a symlink called 'docs' pointing to the 'content' directory does not work (i.e. the job deploying the GitHub pages fails instantly). The other way around, i.e. hosting the resources in the 'docs' directory and having 'content' be the symlink was not accepted by the Apache backend in my tests, but it seemed to work with the previous setup on the master. So maybe this setup could work