Skip to content

pdeters/js-docker-mk

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 

Repository files navigation

TIBCO JasperReports® Server for minikube

This repository is a fork of the TIBCOSoftware/js-docker repository.

This project intends to build and deploy a minimal TIBCO JasperReports® Server Professional Edition installation to a local Kubernetes cluster using minikube.

JasperReports Server minikube cluster

This project contains a bash script that aims to codify the steps found in the base repo docs here:


Prerequisites

  1. Docker-engine (19.x+)
  2. minikube
  3. Docker Compose (3.9+)
  4. Helm 3.5
  5. kubectl commandline tool
  6. TIBCO JasperReports® Server
  7. Minimal Knowledge of Docker and K8s

Setup

Clone the project

git clone git@github.com:pdeters/js-docker-mk.git
cd js-docker-mk

Download a commercial edition of TIBCO JasperReports® Server WAR File installer zip into the current directory.

  • Currently this works for exactly TIB_js-jrs_8.1.0_bin.zip

Obtain a JRS license file and place it in the current directory as jasperserver.license

Run

Run the default setup script:

  sh minikube/setup.sh

This script will delete and recreate minikube, create and customize necessary files in the base repository and unzipped installer directories, then build and deploy the Docker images to minikube using Docker Compose and Helm.


Run the default setup script, accepting all prompts:

The default setup script will prompt you before doing anything destructive (such as running minikube delete), but you can skip these prompots using the -f flag:

  sh minikube/setup.sh -f

Run the setup script, with a custom k8s namespace:

By default this script will install all k8s resources in the jasper-reports namespace, but you may also provide your own using the -n flag:

  sh minikube/setup.sh -n custom-namespace

Run the cleanup script:

By design this script aims to not modify any of the asset files in the base repository, so once the script has completed you should expect to see several modified and untracked files (aside from the zip and license files you initially setup).

It's not reccomened to commit these changes, so after the setup script completes, you can run it again to cleanup using the -c flag:

  sh minikube/setup.sh -c

About

Container deployment of TIBCO JasperReports® Server

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Smarty 61.8%
  • Shell 26.4%
  • Dockerfile 11.8%