[
https://issues.apache.org/jira/browse/JDO-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-788:
---------------------------------
Fix Version/s: JDO 3.2
> Decide what to do with GitHub pages setup
> -----------------------------------------
>
> Key: JDO-788
> URL: https://issues.apache.org/jira/browse/JDO-788
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3.1
> Reporter: Tobias Bouschen
> Priority: Minor
> Fix For: JDO 3.2
>
>
> The JDO website is currently also being hosted as GitHub pages under
> [https://apache.github.io/db-jdo-site/.|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|https://apache.github.io/db-jdo-site/] 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
