Skip to content

Latest commit

 

History

History
233 lines (163 loc) · 7.63 KB

README.md

File metadata and controls

233 lines (163 loc) · 7.63 KB
Raw

next stable

SAEON Data Portal

A suite of services that provide a platform for searching and exploring SAEON-curated datasets

README Contents

Overview

The SAEON Data Portal is a tool for searching SAEON's curated metadata.

The stack

Quick start

Setup the repository for development on a local machine. The Node.js and React services are run using a local installation of Node.js, and dependent services (Mongo, Elasticsearch) are run via Docker containers.

Mostly configuration params have sensible defaults, only the API needs to be explicitly configured with authentication credentials, without which there will be no data available to the catalogue software (the server crashes on startup with a helpful error message in this case).

System requirements

  1. Docker Engine
  2. Node.js v19.5.0

Start a local MongoDB server

Start the ELK stack locally

Install dependencies and run the services

# Download the source code
git clone [email protected]:SAEON/data-portal.git sdp
cd sdp

# Install the chomp CLI
npm install -g chomp

# Update repository git configuration
chomp git:configure

# Install package dependencies. From the root of this repository:
npm install \
  && cd api \
  && npm install \
  && cd ../clients \
  && npm install \
  && cd ..

# Open a terminal window to run the API
cd api
chomp --watch

# Open a terminal window to run the clients
cd clients
chomp --watch

Load catalogue data on first use

The first time you use the Data Portal on a local you need to load metadata from the catalogue into Elasticsearch. There is a CLI to do this (refer to the section below on the CLI).

Here's the TLDR: from the root of this repository:

cd api
source env.sh
sdp integrations saeon --run

NOTE: if you are integrating against the development version of the ODP, then you need to allow for self-signed certificates (NODE_TLS_REJECT_UNAUTHORIZED=0). In this case the command is:

NODE_TLS_REJECT_UNAUTHORIZED=0 sdp integrations saeon --run

Command Line Interface (CLI)

The application includes a CLI to run tasks - for example, triggering the ODP integration manually, building sitemaps manually, running database migration scripts, etc.

Running the CLI in a dockerized environment

The CLI is packaged into the Docker image at build time. Use the sdp command in the context of the docker container. Even if the container is part of a docker stack, it's necessary to use a specific container on a specific host, so these instructions are for docker swarm or otherwise. For example:

# List active containers
docker container ls

# Get the container ID. For example: 0419726a1bec, and login to the container
docker container exec -it 0419726a1bec sh

# Run the CLI - the commands are documented in the CLI output
sdp

Running the CLI in a local/non-dockerized environment

From the root of the source code repository:

cd api

# This updates the $PATH environment variable so that the `sdp` command works
source env.sh

# Run the CLI
sdp

Deployment

Although the client and API are treated as separate during development, when deploying the software the client must be served via the API server. SEO and other features are configured this way.

NOTE: Since the client is configured at image build time, deployments to separate hostnames require building separate Docker images.

Build and Deploy a Docker image

Please refer to source code for build time & runtime configuration options (or request additional documentation). But in short, the domain of the image currently has to be specified at build time (when the React.js client is built via Webpack. Here is a minimum working example for deploying a Docker image on localhost.

Build Docker image locally

From the root of the repository:

docker build -t sdp_local .

Run that image

NETWORK=saeon_local

# Assuming containers named "mongo" and "elasticsearch" can be found on the "saeon_local" network

# Control what ODP records get included by mounting a js file at ODP_FILTER_PATH
# Control what filters are shown on the /records path by mounting a JSON file at CLIENT_FILTER_CONFIG_PATH

# Or if you want to test the image built above
IMAGE=sdp_local:latest

docker \
  run \
    -v $(pwd)/api/odp-filter.js:/app/odp-filter.js \
    -v $(pwd)/clients/client-filters.json:/app/client-filters.json \
    -e DEFAULT_SYSADMIN_EMAIL_ADDRESSES="..." \
    -e MONGO_DB_ADDRESS="mongodb://mongo:27017" \
    -e ELASTICSEARCH_ADDRESS="http://elasticsearch:9200" \
    -e ODP_HOSTNAME=odp.saeon.ac.za \
    -e ODP_CLIENT_SECRET=... \
    -e ODP_SSO_CLIENT_SECRET=... \
    -e ODP_CLIENT_AUTH_SCOPES=ODP.Catalogue \
    -e ODP_FILTER_PATH=/app/odp-filter.js \
    -e CLIENT_FILTER_CONFIG_PATH=/app/client-filters.json \
    -p 3000:3000 \
    -d \
    --rm \
    --name sdp_local \
    --net=$NETWORK \
    $IMAGE

SAEON production/dev deployments

Deploy the latest docker image configured for catalogue.saeon.ac.za using the same docker run command as above, but specify the correct Docker image:

IMAGE=ghcr.io/saeon/saeon-data-portal:latest
# or IMAGE=ghcr.io/saeon/sdp_next:dev

NETWORK=... # Refer to above

SAEON production and development deployments are configured as Docker stacks.

Deploy from source code

To deploy from source code directly (i.e. without Dockerizing the application), follow these steps.

From the root of the repository:

chomp build
cd api

# Either start node via chomp
chomp

# Or run node directly
node \
  --no-warnings \
  --experimental-json-modules \
  src/index.js

# or start via the shell script
source env.sh
start

API documentation

CLient documentation