Development
Develop and test integrations in GitBook.
After bootstrapping your integration with the GitBook CLI, you can continue using the CLI to develop and test your app.
Publish your integration
Before you're able to develop your integration, you will first need to publish it. You can do this by running the following command in the root directory:
By default (defined in the CLI-generated gitbook-manifest.yaml
), your integration will be published privately, and owned by the organization specified in the manifest.
After publishing your integration, the CLI will give you a link to install your integration into the organization you’ve set.
You need to install your app into at least 1 space or organization in order to develop it locally. Make sure to note the spaceId
of the space you're installing it into for step 2.
Start your integration’s development server
While inside the root directory of your app, run:
This will start a development server tied to the space specified in the command.
After running the command, the CLI will generate a gitbook-dev.yaml
file that contains the spaceId
needed to establish the connection while you continue to develop your app. You can change this at any time in by re-running gitbook dev <spaceId>
.
Running this command will start a development server for use by the integration only. You do not need to navigate to the port the server is running on. All integration traffic to the specified space will automatically be served from your local server instead of the published version.
Develop your integration
It's recommended that you disable browser caching for the most optimal experience when developing your app.
Any logs sent to the console or made through your integration's RuntimeContext
will be surfaced in your browser's console.
Any UI changes made to your integration will need a browser refresh in order to be visible.
FAQ
Last updated
Was this helpful?