Configure development and production builds for Sphinx projects#

This document describes how to configure new Sphinx documentation projects for development and production.

Configure a project for development#

Development projects are built and deployed to the domain instead of

These projects do not show up on the docs landing page, and you have to update the project configuration file to ensure that the content is excluded from search indexing.

If you want to move a development project to production, update the nexus-control configuration by following the steps to configure a production build.

Complete the following steps to build and deploy a documentation project to the development environment.

  1. Add a new content repository to deconst.
  2. Enable Strider build automation.
  3. Configure a project for development builds.
  4. Review Strider build information.

Configure a project for production#

Complete the following steps to build and deploy a documentation project to the production environment.

  1. Add a new content repository to deconst.
  2. Enable Strider build automation.
  3. Configure project for production builds.
  4. Review Strider build information.
  5. Add documentation to landing page.


Existing branches are continuously integrated by Strider. Merging a pull request to a branch that is currently being published updates automatically.

Add a new content repository to Deconst#

You can add a new content repository branch to Deconst if your content is written in reStructuredText (RST) or Markdown, and hosted in a git repository on

  1. Update the GitHub repository settings to enable deconst to create a Strider build job for your project.

    1. In the GitHub UI, click Settings > Collaborators & teams.

    2. Add the rackernexus service account as a collaborator with Admin privileges.

      GitHub will send an invitation requesting that rackernexus join the repository.

    3. In the Deconst Slack channel, request the deconst administrator to accept the GitHub invitation sent to the rackernexus service account.

  2. Create a deconst configuration file for the project you want to build.

    1. In the content repository branch, navigate to the root folder for your documentation project.

    2. Add the _deconst.json.

    3. Add the following parameters to the new file.

      • contentIDBase: A content ID to identify the content produced from this directory. It must be a unique ID to all content repositories published to Deconst.
      • githubUrl: The GitHub URL for the content repository.
      • githubBranch: Specifies the target branch for “edit on GitHub” link if your project is on a branch other than master.
      • preferGitHubIssues: Specifies whether the documentation interface provides a Submit issue link to open a GitHub issue or an ‘Edit on Github`link to edit documentation source.

      For example:

          "contentIDBase": "",
          "githubUrl": "",
          "githubBranch": "v13",
          "meta": {
              "preferGithubIssues": true
  3. If the project is a development project, update the project configuration file to exclude the content from search indexing.

    For Sphinx projects, update the file with the following configuration settings:

    # Exclude content from elastic search index
    deconst_default_unsearchable = True

For more information on adding a new content repository, see the deconst documentation.

Enable Strider build automation#

You can generate the Strider production build job automatically by adding the source repository URL to the Nexus control configuration. For each repository, you can configure builds for one or more branches. By default, Strider builds from the master branch. If you want to build from other branches, you must specify the branch name.

Prerequisite The source repository must have the rackernexus GitHub ID configured as an outside collaborator with Admin access.

  1. Add the repository to the content-repositories.json file. For example:

    { "kind": "github", "project": "rackerlabs/docs-rpc" },
  2. To add builds for a specific branch, add the branch name.

    For example, the following specification shows the configuration to build from master, v10, v11, and v12 branches:

    { "kind": "github", "project": "rackerlabs/docs-rpc", "branches": [master, "v10", "v11", "v12"] },
  3. Commit your changes, submit a PR and merge it.

The next time you submit a PR to the repository branch for your project, the Strider build is created. You should see a preview link in the PR indicating that the build ran successfully.

Configure a project for development builds#

To configure a development build on a branch, update the site configuration in the nexus-control content and template mapping files. These files are in the nexus control repository that manages the build and deployment process for the Rackspace documentation websites.

The content mapping file associates the content in a source repository with the URL where the content is deployed. The content source repository is identified by the unique content ID for the project, the contentIDBase specified in the _deconst.json file.

The template mapping file specifies the template applied to content when a user requests content. For example, for book-style content with previous and next links, use the user-guide.html template. For single page topics, use the single-page.html template.

  1. Add the content mapping to config/content.d/

    The following example shows the specification to deploy content from the docs-rpc master branch to the /docs/private-cloud/rpc/master/ path on the development staging server:

    "/docs/private-cloud/rpc/master/": "",
  2. Add the template mapping to config/routes.d/ configuration file.

    The following example shows the mapping to apply the user guide template to all Rackspace Private Cloud content:

    "^/docs/private-cloud/": "",

After you have updated the configuration files, submit a PR to the branch in the project repository that you added. Wait for the PR to update with the preview link to review your content. See Review Strider build information.

If the preview link fails, or if the formatting does not look right, verify that the nexus-control configuration includes the branch in the content and template mapping files, and that the repository has been added to the content.repositories file.


You can move a project from development to production by following the process to add a production build.

Configure a project for production builds#

If you want to build and deploy a project to production, update the nexus-control configuration files for to define the URL for content deployment and to specify the template to apply during the build process.

  1. Add the contentIDBase for the branch content to the content.d/ configuration file. For example:



    The contentIDBase is defined in the _deconst.json file located in the content repository branch.

  2. Check the routes.d/ configuration file to confirm that a template has been listed for the URL pattern you specified for the branch. For example:

    "^/docs/private-cloud/": "user-guide.html",
  3. After you have updated the configuration files, submit a PR to the branch in your project repository and wait for PR to update with the preview link to review your content.

Review Strider build information#


To create a Strider build for a documentation project, complete the nexus-control configuration updates to :ref`Enable Strider build automation <Enable Strider build automation>`.

Use the following information to view Strider build information:

  • Review a list of Strider build jobs for documentation projects at

    If you get a 404 error, log in with your GitHub ID. If you still can’t view the builds, open an issue to request access.

  • To view builds for a repository, look for the build badge at the top of the readme file. It indicates whether the most recent build passed or failed. Click the badge to open the build log.

  • You can view the build log for a PR from the GitHub interface. When you submit the PR, a GitHub webhook triggers the Strider build process. Build results are added to the PR.

    • If the build fails, click the Details.
    • If the build passes, click Show all checks. Then, click Details.


For more information about deconst, see the`deconst documentation <>`_.

Add documentation to the landing page#

After you add a documentation project to production, update the landing page <https:\developer.rackspace.comdocs> to add the documentation title to the documentation menu.

  1. Update the file in the new branch to restore search indexing in production. Comment out the search index setting:

    # Exclude content from elastic search index
    # deconst_default_unsearchable = True
  2. Update docs-quickstart to add the new documents to the appropriate card on the landing page. For example:

    <h5>Rackspace Private Cloud v12</h5>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-admin/">Administrator Guide</a></li>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-faq-external/">Technical FAQ</a></li>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-ops/">Operations Guide</a></li>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-releasenotes">Release Notes</a></li>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-swift">Standalone Object Storage Guide</a></li>
        <li><a href="/docs/private-cloud/rpc/v13/rpc-upgrade">Upgrade Guide</a></li>
  3. Commit the menu page updates and submit a PR.

  4. In the GitHub view for the PR, click the preview link to to make sure the updates render correctly.

    If the content does not build correctly, review the build log.

  5. After verifying the content, merge the PR to deploy to production.

  6. Check the landing page to make sure the content is deployed correctly.


If the content is not deployed on the landing page, verify that the rackerlabs/docs-quickstart project is building successfully in If the build is stuck, click on the Retest & Deploy icon.