From 2fd028c8df23800b7ef458826f68d87983c165e1 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Mon, 4 Dec 2017 17:17:43 +0000 Subject: [PATCH] Deploy website Deploy website version based on f58d5ce491b759e62f65b1c7982eeddf570d2948 --- docs/en/publishing.html | 33 +++++++++++++++++++-------------- 1 file changed, 19 insertions(+), 14 deletions(-) diff --git a/docs/en/publishing.html b/docs/en/publishing.html index 77965b039c..791c6c3033 100644 --- a/docs/en/publishing.html +++ b/docs/en/publishing.html @@ -21,31 +21,36 @@

Even if your repo is private, anything published to a gh-pages branch will be public.

-

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script. The required parameters are:

+

Most of the work to publish to GitHub pages is done for you automatically through the publish-gh-pages script. You just need to determine the values for a few parameters required by the script.

+

Two of the required parameters are set in the siteConfig.js:

+ +
+

While we recommend setting the above in siteConfig.js, you can also use environment variables ORGANIZATION_NAME and PROJECT_NAME.

+
+

One of the required parameters are set as environment variables:

+

There is also an optional parameter that is set as an environment variable. If nothing is set for this variable, then the current branch will be used.

+

We currently require the published documentation to be served from the gh-pages branch in your GitHub repo.

-
-

The reason we prefix some of these parameters with CIRCLE is because Docusaurus recommends publishing your documentation continuously when changes are committed via CircleCI.

-
-

Once you have the paremeter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

+

Once you have the parameter value information, you can go ahead and run the publish script, ensuring you have inserted your own values inside the various parameter placeholders:

To run the script directly from the command-line, you can use the following, filling in the parameter values as appropriate.

GIT_USER=<GIT_USER> \
-  CIRCLE_PROJECT_USERNAME=<CIRCLE_PROJECT_USERNAME> \
-  CIRCLE_PROJECT_REPONAME=<CIRCLE_PROJECT_REPONAME> \
-  CIRCLE_BRANCH=master \
+  CURRENT_BRANCH=master \
   yarn run publish-gh-pages # or `npm run publish-gh-pages`
-

The specified GIT_USER must have push access to the repository specified in the combination of CIRCLE_PROJECT_USERNAME and CIRCLE_PROJECT_REPONAME.

+

The specified GIT_USER must have push access to the repository specified in the combination of organizationName and projectName.

-

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://CIRCLE_PROJECT_USERNAME.github.io/CIRCLE_PROJECT_REPONAME, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://facebookexperimental.github.io/docusaurus), because it is served from the gh-pages branch of the https://github.com/facebookexperimental/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

+

You should now be able to load your website by visiting its GitHub Pages URL, which could be something along the lines of https://organizationName.github.io/projectName, or a custom domain if you have set that up. For example, Docusaurus' own GitHub Pages URL is https://docusaurus.io (it can also be accessed via https://facebookexperimental.github.io/docusaurus), because it is served from the gh-pages branch of the https://github.com/facebookexperimental/docusaurus GitHub repo. We highly encourage reading through the GitHub Pages documentation to learn more about how this hosting solution works.

You can run the command above any time you update the docs and wish to deploy the changes to your site. Running the script manually may be fine for sites where the documentation rarely changes and it is not too much of an inconvenience to remember to manually deploy changes.

However, you can automate the publishing process with continuous integration (CI).

Automating Deployments Using Continuous Integration

@@ -85,7 +90,7 @@ deployment:

Make sure to replace <GIT_USER> with the actual username of the GitHub account that will be used to publish the documentation.

DO NOT place the actual value of $GITHUB_TOKEN in circle.yml. We already configured that as an environment variable back in Step 3.

-

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the values of CIRCLE_PROJECT_USERNAME, CIRCLE_PROJECT_REPONAME, and CIRCLE_BRANCH are already defined as environment variables within CircleCI and will be picked up by the script automatically.

+

Unlike when you run the publish-gh-pages script manually, when the script runs within the Circle environment, the values of ORGANIZATION_NAME, PROJECT_NAME, and CURRENT_BRANCH are already defined as environment variables within CircleCI and will be picked up by the script automatically.

Now, whenever a new commit lands in master, CircleCI will run your suite of tests and, if everything passes, your website will be deployed via the publish-gh-pages script.