Site backend setup change

[Tobias Bouschen]

Hi all,

after a long discussion with the INFRA team, it seems like we have 
gotten to a point were the problem has almost been resolved.

The issue seemed to be caused by the backend not being set up to handle 
our specific use case. It should work in the future, but to avoid 
putting unnecessary strain on the service I also created a pull request 
to amend the action to preserve the deploy history (see 
https://github.com/apache/db-jdo-site/pull/17).

The only remaining issue with the setup seems to be where the content is 
expected to be located (see 
https://issues.apache.org/jira/browse/INFRA-21326?focusedCommentId=17270643&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17270643).

I am not sure what they mean by getting the "CMS checkout changed," but 
it sounds like something that was configured specifically for the old 
website layout. I am not quite sure how to proceed here. In my opinion, 
it would be easiest to change the backend configuration to expect the 
content to be hosted in the root directory. This avoids having 
additional (and potentially confusing) configuration on our end. But, as 
already mentioned, I am not familiar with the configuration they mentioned.

As this is something that should be discussed before making a decision 
and the interaction with the INFRA team will most like take a while, I 
wanted to bring this issue up now instead of waiting until the next standup.

So what do you think? How should we proceed with the issue regarding 
which directory to host the content in?

Best regards,
Tobias