openlmis-ref-distro

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Import datasources before superse init

Import a datasource on docker run

    • -0
    • +6
    /reporting/superset/datasources/reporting.yaml
Probably "or set..."?

Probably "or set..."?

Probably "Some features..."?

Probably "Some features..."?

changed requisition and reference-ui versions for 3.3.1 release
changed requisition and reference-ui versions for 3.3.1 release
Draft 3.3.1 Patch Release notes

Draft 3.3.1 patch release notes, included disclaimer for review.

    • -0
    • +296
    /docs/source/releases/3.3.1 Patch Release Notes
changed requisition and reference-ui versions for 3.3.1 release
changed requisition and reference-ui versions for 3.3.1 release
OLMIS-4775: Send Reporting Stack Logs to Scalyr (#24)

* OLMIS-4775: Send Reporting Stack Logs to Scalyr

Add support for sending logs from the reporting stack containers to

Scalyr.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

* OLMIS-4775: Make Path to Docker SOCK Configurable

Make the path to the docker socket file to use for the Scalyr service

configurable.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

    • -0
    • +4
    /reporting/scalyr/api_key.json
    • -0
    • +6
    /reporting/scalyr/server_host.json
Using Spring's built-in Redis caching could be cool. Worth researching further and potentially replacing when we start using Redis more.

Using Spring's built-in Redis caching could be cool. Worth researching further and potentially replacing when we start using Redis more.

I know this is a late answer~ Actually I tried starting with Spring Data Redis. 2.x couldn't be used due to lack of compatibility with Spring Boot 1.X however and I had some problem that I no longe...

I know this is a late answer~
Actually I tried starting with Spring Data Redis. 2.x couldn't be used due to lack of compatibility with Spring Boot 1.X however and I had some problem that I no longer remember with latest 1.x of Spring Data Redis...

Merge pull request #23 from jasonrogena/use-onaio-nifi-image

OLMIS-5052: Place Postgres JDBC Lib in libs Dir

OLMIS-5052: Place Postgres JDBC Lib in libs Dir

Place the PostgreSQL JDBC drive in the libs volume since it get's copied

over to a directory on NiFi's classpath. NiFi users hence don't have to

specify the location of the driver when configuration the controller

service.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

    • binary
    /reporting/nifi/assets/postgresql-42.2.3.jar
    • binary
    /reporting/nifi/libs/postgresql-42.2.3.jar
Merge pull request #22 from jasonrogena/use-onaio-nifi-image

OLMIS-5052: Use onaio/nifi Docker Image

Add NiFi External Libs Volume

Add a NiFi volume for placing external libraries (like custom .nar

files) that would be copied over to the lib/ directory inside NiFi's

woking directory before starting NiFi.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

    • -0
    • +0
    /reporting/nifi/libs/.placeholder
OLMIS-5052: Add a NiFi Assets Volume

Add a NiFi assets volume mounted in NiFi's working directory. Place the

PostgreSQL JDBC driver in this volume.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>

    • binary
    /reporting/nifi/assets/postgresql-42.2.3.jar
copy-paste from requisition. Yea I changed all requisition to notification https://review.openlmis.org/static/ogdo0b/2static/images/wiki/icons/emoticons/wink.gif

copy-paste from requisition. Yea I changed all requisition to notification

OLMIS-5069: Generate ERD for notification service
OLMIS-5069: Generate ERD for notification service
OLMIS-5069: added information about notification ERD schema

    • -0
    • +8
    /docs/source/components/erd-notification.rst
updated reference-ui version to 5.1.0

OLMIS-5051: change reporting consul port to not conflict with main consul (#21)

OLMIS-5052: Use onaio/nifi Docker Image

Switch from using apache/nifi to onaio/nifi that has a custom build of

NiFi with an InvokeHTTP Processor that supports authentication over

OAuth2.

Signed-off-by: Jason Rogena <jasonrogena@gmail.com>