This is an automated email from the ASF dual-hosted git repository.
rubenada pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/calcite.git
The following commit(s) were added to refs/heads/main by this push:
new 7939fa2163 Site Readme: add the old instructions to manually publish
the site, in case the automatic process fails
7939fa2163 is described below
commit 7939fa2163467205726764fb2e575f8b289c1b8b
Author: Ruben Quesada Lopez <[email protected]>
AuthorDate: Thu Jul 30 11:41:06 2026 +0100
Site Readme: add the old instructions to manually publish the site, in case
the automatic process fails
---
site/README.md | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/site/README.md b/site/README.md
index 9cba819dcb..a5759b50fd 100644
--- a/site/README.md
+++ b/site/README.md
@@ -72,3 +72,45 @@ ## Release publishing
you only need to push the new tag 'calcite-x.y.z' to [Calcite Github
repo](https://github.com/apache/calcite),
and the Github workflow will do all the rest.
The rules and scripts are in
`.github/workflows/publish-website-on-release.yml`.
+
+## Legacy method: manually pushing to site
+
+This should normally **not** be required any more, but in case the automatic
publication fails,
+these are the (legacy) steps to manually publish the site:
+- Push the commit with the changes to the `main` branch of this repository.
+- Cherry-pick the commit from the `main` branch to the `site` branch of this
repository.
+- Checkout the `site` branch and build the website using
[docker-compose](#previewing-the-website-locally-using-docker).
+- Commit the generated content to the `main` branch of the `calcite-site`
repository following these steps:
+
+1. `cd site/target`
+2. `git init`
+3. `git remote add origin [email protected]:apache/calcite-site.git`
+4. `git fetch`
+5. `git reset origin/main --soft`
+
+If you have not regenerated the javadoc (you shouldn't unless you are
publishing a new release)
+and they are missing, restore them:
+
+6. `git reset -- javadocAggregate/`
+7. `git checkout -- javadocAggregate/`
+
+Restore the avatica site
+
+8. `git reset -- avatica/`
+9. `git checkout -- avatica/`
+
+Push the changes
+10. `git add .`
+11. Commit: `git commit -m "Your commit message goes here"`
+12. Push the site: `git push origin main`
+
+Within a few minutes, gitpubsub should kick in and you'll be able to
+see the results at
+[calcite.apache.org](https://calcite.apache.org/).
+
+This process also publishes Avatica's web site. Avatica's web site has
+separate source (under `avatica/site`) but configures Jekyll to
+generate files to `site/target/avatica`, which becomes an
+[avatica](https://calcite.apache.org/avatica)
+sub-directory when deployed. See
+[Avatica site
README](https://github.com/apache/calcite-avatica/blob/main/site/README.md).
