3pp-mirror/docusaurus
1
0
Fork 0
mirror of https://github.com/facebook/docusaurus.git synced 2025-06-05 12:22:45 +02:00
Code Issues Projects Releases Packages Wiki Activity

update website [ci skip]

Browse source
This commit is contained in:
Hector Ramos 2017-10-24 14:05:25 -07:00
parent 551c098fd0
commit 247b556ea9
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/en/publishing.html
View file

@ -31,7 +31,7 @@
<p>You can run the command above any time you update the docs and wish to deploy the changes to your site. That's usually fine for sites where the documentation rarely changes, where it's not too much of an inconvenience to remember to manually deploy changes. Now, if you're wondering if this process can be automated in any way, keep reading...</p>
<h2><a class="anchor" name="automating-deployments-using-continuous-integration"></a>Automating Deployments Using Continuous Integration <a class="hash-link" href="#automating-deployments-using-continuous-integration">#</a></h2>
<p>Continuous integration services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the <code>publish-gh-pages</code> script whenever your docs get updated. In the following section we'll be covering how to do just that using Circle CI, a popular continuous integration service provider.</p>
<h3><a class="anchor" name="using-circle-ci-10"></a>Using Circle CI 1.0 <a class="hash-link" href="#using-circle-ci-10">#</a></h3>
<h3><a class="anchor" name="using-circle-ci"></a>Using Circle CI <a class="hash-link" href="#using-circle-ci">#</a></h3>
<p>If you're already using Circle CI for your project, all you need to do to enable automatic deployments is to configure Circle to run the <code>publish-gh-pages</code> script as part of the deployment step.</p>
<ol>
<li>Go to https://github.com/settings/tokens and generate a new token, granting it full control of private repositories through the <code>repo</code> access scope. Store this token in a safe place, making sure to not share it with anyone. This token can be used to authenticate GitHub actions on your behalf in place of your GitHub password.</li>