kevinjqliu commented on issue #178: URL: https://github.com/apache/datafusion-site/issues/178#issuecomment-4431641618
We reverted both #179 and #180. The deployment pattern for this blog site requires URL redirection. With the reverts in place, Giscus now loads correctly on the redirected URLs. **That was the actual user-facing problem.** I'm not entirely sure why Giscus failed to load before and works now after the reverts. The `.htaccess` and `output/` content should be the same as they were previously, so the difference isn't obvious. If anyone has insight, I'd be curious to hear it. (Perhaps it was cached?) A note on why the redirect is needed (for future reference): The `https://datafusion.apache.org/` domain is shared by both the main site and the blog site. The blog site is mounted at `https://datafusion.apache.org/blog/`. The publish workflow must publish into a subdirectory (`output/`) on the deploy branch so the blog content lives in `https://datafusion.apache.org/blog/output/`. We can't write to the branch root, because the [ASF pelican action](https://github.com/apache/infrastructure-actions/tree/main/pelican) runs `rm -rf ${output}` before copying, which would destroy the other files there (`.htaccess`, `.asf.yaml`, etc.). As a result, all blog content lives in `output/` on the `asf-site` branch, and `.htaccess` rewrites are required to serve it under the user-facing `https://datafusion.apache.org/blog/...` URLs. Closing this out. No further fix planned. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
