The online documentation uses doxygen to build the reference documentation for the bes and then pushes those HTML pages up to a GitHub Pages website.
The process is simple, but involves some 'tricks' that make the process hard to implement in a robust way.
What to do:
- Checkout the gh-pages branch of the repo. This is an orphaned branch.
- Remove the 'html' directory and its contents.
- Commit that change (but don't push that commit - pushing comes later).
- Switch back to the master branch.
- There should be no 'html' directory - if there is, remove it.
- Build the doxygen pages, that process will make the 'html' directory
- Switch back to the gh-pages branch
- Add the 'html' directory (and thus its contents) to the gh-pages branch
- Commit that change.
- Push the gh-pages branch
- Switch back to master/main
- Check that the documentation built and uploaded to the GitHb Pages site.
Here's the command sequence, assuming you are on the branch 'master':
git checkout gh-pages
git rm -rf html
git commit -m "Removed old docs"
git checkout master
doxygen doxy.conf
git checkout gh-pages
git add --force html
git commit -m "New docs"
git push
git checkout master
Then, in a browser, goto the BES reference documentation (https://opendap.github.io/bes/html/).
How to make the special 'orphaned branch' gh-pages
Assuming you are on 'master/main:'
git checkout --orphan gh-pages
git reset --hard
git commit --allow-empty -m "Initializing gh-pages branch"
git push origin gh-pages
git checkout master