78e9f45214
Related issue scylladb/sphinx-scylladb-theme#88 Once this commit is merged, the docs will be published under the new domain name https://scylla.docs.scylladb.com Frequently asked questions: Should we change the links in the README/docs folder? GitHub automatically handles the redirections. For example, https://scylladb.github.io/sphinx-scylladb-theme/stable/examples/index.html redirects to https://sphinx-theme.scylladb.com/stable/examples/index.html Nevertheless, it would be great to change URLs progressively to avoid the 301 redirections. Do I need to add this new domain in the custom dns domain section on GitHub settings? It is not necessary. We have already edited the DNS for this domain and the theme creates programmatically the required CNAME file. If everything goes well, GitHub should detect the new URL after this PR is merged. The DNS doesn't seem to have the right SSL certificates GitHub handles the certificate provisioning but is not aware of the subdomain for this repo yet. make multi-version will create a new file "CNAME". This is published in gh-pages branch, therefore GitHub should create the missing cert. Closes #7877
20 lines
497 B
Bash
Executable File
20 lines
497 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# Copy contents
|
|
mkdir gh-pages
|
|
cp -r ./docs/_build/dirhtml/. gh-pages
|
|
./docs/_utils/redirect.sh > gh-pages/index.html
|
|
|
|
# Create gh-pages branch
|
|
cd gh-pages
|
|
git init
|
|
git config --local user.email "action@scylladb.com"
|
|
git config --local user.name "GitHub Action"
|
|
git remote add origin "https://x-access-token:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git"
|
|
git checkout -b gh-pages
|
|
|
|
# Deploy
|
|
git add .
|
|
git commit -m "Publish docs" || true
|
|
git push origin gh-pages --force
|