Explore

Adding Allegrograph to your FDP Setup

Option 1: Deploying Allegrograph on the same link as your FDP

Option 2: Deploying Allegrograph on a subdomain (Recommended)

From our previous setup we used Ubuntu 24.04 and in there setup Docker to manage our containers and serve them online using NGINX as our reverse proxy. In this documentation we will extend our HDS capability by adding

Allegrograph⁠

to our setup.

Prerequisite

Have already followed the

FDP deployment documentation⁠

and implemented to completion.

There are two ways to serve Allegrograph on your server

Deploying Allegrograph on the same link as your FDP

Deploying Allegrograph on a subdomain (Recommended)

Pros and Cons

Pros and Cons

Name

Pros

Cons

Deploying Allegrograph on the same link as your FDP e.g. fdp.example.com/agraph

Easier to manage when routing the Agraph service using NGINX

Easier to manage DNS and SSL certificate issuing

High chances of misconfiguring your routing setup

Confusion on exact Agraph link since the same subdomain is used to access both systems

Creating a subdomain and assigning it to Allegrograph e.g. agraph.example.com

Cleaner and managable setup

Easier troubleshooting both FDP and Agraph

Technical guidance needed to setup the routing and issueance of SSL certificate and setup of DNS records

There are no rows in this table

⁠

Given this, we will create both documentation processes for you to choose.

⁠

Option 1: Deploying Allegrograph on the same link as your FDP

⁠

Option 2: Deploying Allegrograph on a subdomain (Recommended)

⁠

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.