Author: John Blischak
Date: 2025-08-18

# Alternative strategies for deploying workflowr websites

### workflowr version 1.7.2

#### John Blischak

#### 2025-08-18

## Introduction

The Getting Started vignette provides instructions for deploying the workflowr website using the service GitHub Pages because it is quick and convenient. However, the static website created by workflowr can be deployed using any strategy you like. Below are instructions for deploying the workflowr website contributed by other workflowr users. If you would like to contribute instructions for another deployment strategy, please fork the workflowr repository on GitHub and add your instructions to this file. If you need any assistance with this, please don’t hesitate to open an Issue.

## Amazon S3 (password-protected)

Another way to privately share your workflowr site is by uploading it to Amazon S3. S3 is an object storage service for the Amazon cloud, and can be used to host static websites. Basic HTTP authentication can be accomplished using CloudFront, Amazon’s content delivery network, and Lamba@Edge, which enables the execution of serverless functions to customize content delivered by the CDN. This blog post goes into more detail about what that all means. Some templates for scripting the process are here.

Contributed by E. David Aja (edavidaja).

## GitLab Pages

To deploy your workflowr website with GitLab Pages, you can use the function `wflow_use_gitlab()`. You can choose if the site is public or private. For more details, please see the dedicated vignette Hosting workflowr websites using GitLab.