Home

Welcome to the study_finder wiki!

Aside from the documentation provided in the readme, I thought I'd add some more notes as I go through setting this up again from a clean install.

First off, if you're setting this up and don't have an LDAP server (or active directory) you're going to need to decide how you want to handle authentication for researchers and admins. "easy and works but won't scale" would be to run a docker image of openldap with a couple of users and call it a day.

Some notes I'm putting together. There are a number of environment variables that can influence things...examples: in the web container, in "production" mode you'll need (at least) DATABASE_URL=postgres://study:whateverthepasswordis@yourpostgreshostname:5432/databasename' Alternatively, if you fork the codebase, you can edit database.yml and configure whatever database connection info you want. You'll also want to think about the differences between development/test/production if you're having developers tweak any of the code.

On the web container side, you'll also need to identify what the endpoints/credentials are for elasticsearch and ldap. In general you're a little bit on your own about how this might fit into your exact environment. I will say that some of the LDAP authentication info is buried in the /app/lib/modules/ldap.rb file...depending on your LDAP schema, you might need to make some adjustments so that things don't blow up in your face.

As of 2025-05-29, we're exploring what is necessary (versus nice to have) on the elasticsearch side of the house, more to follow as we dig in.