Publishing to a Git Pipeline or Web Server

When you publish content, by default the output is downloaded in a zip file. There are several options for how to publish that content live to your end users.

Publish Manually to Your Web Server

The contents of the default zip download can be uploaded to any web server of your choice, for example via an FTP client. To do so, simply upload the contents of the out folder in the zip file to your server.

Publish to Amazon Web Services S3 (Amazon S3)

awss3.png

Paligo has Continuous Integration (CI) support for Amazon Web Services S3 (Amazon S3). This means you can create content in Paligo, such as PDFs or an HTML help center, and publish it to Amazon S3 so that it is instantly live to your end users.

See Amazon S3 Integration for more on how to do this.

Publish to a BitBucket Pipeline

bitbucket.png

Paligo has Continuous Integration (CI) support for Bitbucket. This means you can create content in Paligo, such as PDFs or an HTML help center, and publish it to Bitbucket. When the content is uploaded to Bitbucket, you can unzip it (automatically if you so choose) to make it instantly available live to your end users.

See Bitbucket Integration for more on how to do this.

Publish to a GitHub Pipeline

github.jpg

Paligo has Continuous Integration (CI) support for GitHub. This means you can create content in Paligo, such as PDFs or an HTML help center, and publish it to GitHub. When the content is uploaded to GitHub, you can unzip it (automatically if you so choose) to make it instantly available live to your end users.

See GitHub Integration for more on how to do this.

Publish Directly to Your Web Server Via FTP

ftp.png

With the FTP (File Transfer Protocol) integration, you can publish your Paligo content, such as an HTML5 help center, directly to your web site.

See FTP Integration for more on how to do this.