You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy the documentation automatically to the branch gh-pages and Github Actions.
Below are some pointers to deploy Sphinx documentation from the repository to GitHub Pages and configure it to work with a subdomain (e.g., evideo.eventyay.com), follow these steps:
1. Prepare Your Sphinx Documentation
Set Up Your Sphinx Project:
If not already set up, initialize a Sphinx project in your repository:
sphinx-quickstart
Customize the conf.py file and your documentation content as needed.
Build Your Documentation Locally:
Run the following to generate the HTML files:
make html
The generated files will typically be in the _build/html directory.
2. Create the gh-pages Branch
Create a new orphan branch for GitHub Pages:
git checkout --orphan gh-pages
Clean up the branch:
git rm -rf .
Add a .gitkeep file for now to initialize the branch:
Deploy the documentation automatically to the branch gh-pages and Github Actions.
Below are some pointers to deploy Sphinx documentation from the repository to GitHub Pages and configure it to work with a subdomain (e.g., evideo.eventyay.com), follow these steps:
1. Prepare Your Sphinx Documentation
Set Up Your Sphinx Project:
conf.py
file and your documentation content as needed.Build Your Documentation Locally:
_build/html
directory.2. Create the
gh-pages
Branchgit rm -rf .
.gitkeep
file for now to initialize the branch:touch .gitkeep git add .gitkeep git commit -m "Initialize gh-pages branch" git push origin gh-pages
3. Configure Automated Deployment via GitHub Actions
.github/workflows/deploy.yml
:main
branch.4. Add the Custom Subdomain
In the
gh-pages
branch, create a file namedCNAME
:Ensure the
CNAME
file is present in the root directory of thegh-pages
branch.5. Configure Your DNS
evideo.eventyay.com
to:6. Verify the Deployment
gh-pages
branch.The text was updated successfully, but these errors were encountered: