Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1

The material in this document is for informational purposes only. This guide assumes that the most recent version of Rampiva Automate is in use unless otherwise noted in the prerequisites. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.

Introduction

This article provides an example configuration for publishing Nuix Rampiva behind an nginx reverse proxy under a subfolder.

Prerequisites 

  • Nuix Rampiva v8.0 or later

  • nginx

Instructions

A. Sample nginx location section configuration

  location /app/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    # Set the X-Forwarded-Base-Uri header to the public URI under which the app is accessible externally
    proxy_set_header X-Forwarded-Base-Uri http://external.rampiva.com/app/;
    proxy_set_header X-Forwarded-Proto $scheme;

    # To enable File Uploads, set the client_max_body_size to the maximum file size that will be supported
    client_max_body_size 1G;

    rewrite ^/app/?(.*) /$1 break;

    # Set proxy_pass to the internal app URI
    proxy_pass http://10.0.0.1:81;
  }

This sample configuration is not optimal for data uploads, which will first be sent to the proxy server and then proxied to Nuix Rampiva. For use with data uploads, configure a streaming proxy server instead.

  • No labels