add config files for plugins?

[dmd]

I'd like to use the xnat-ldap-plugin. It seems to want me to write a file into /data/xnat/home/config, but that path seems to be internal to this container, not mounted from outside.

What's the right thing to do?

[kelseym]

Take a look at ./xnat/Dockerfile line: 13
You can add a line and copy the pattern "ADD foo.config /data/xnat/home/config/foo.config

Once you rebuild the xnat container:
docker-compose build xnat-web
and restart xnat-web:
docker-compose restart xnat-web

you should be set to go.

[tclose]

Hi Daniel, If you are interested, we are maintaining a fork of the docker compose, https://github.com/MonashBI/xnat-docker-compose, which is set up to keep the configuration files outside of the containers. Cheers, Tom

…

On Wed, 19 Feb 2020 at 08:55, kelseym ***@***.***> wrote: Take a look at ./xnat/Dockerfile line: 13 You can add a line and copy the pattern "ADD foo.config /data/xnat/home/config/foo.config Once you rebuild the xnat container: docker-compose build xnat-web and restart xnat-web: docker-compose restart xnat-web you should be set to go. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#27?email_source=notifications&email_token=AAIBRFXGKT2QOM46V6AM4IDRDRKMRA5CNFSM4KXLUKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMFPBAI#issuecomment-587919489>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIBRFQYXPMHPMLUGAB5FSLRDRKMRANCNFSM4KXLUKQA> .

-- *THOMAS G. CLOSE, PHD* Imaging Informatics Officer *Monash Biomedical Imaging* Monash University Room 139, 770 Blackburn Rd Clayton Campus, Clayton VIC 3800 Australia T: +61 3 9902 9804 M: +61 491 141 390 E: [email protected] mbi.monash.edu.au

[johnflavin]

You're keeping all the good stuff for yourselves on a fork? Come on, Tom, merge that stuff back in!

[tclose]

Okay sure, I didn't want to presume everyone would want it set it up just the way I like it :) I will open a pull request once I iron out all the merge conflicts. The authentication configure script has an option to set up authentication against the Australian Authentication Federation, which probably isn't that relevant to most deployments, but you can safely ignore it. I have also heard there is a bug with the OpenID authentication that still needs ironing out so don't try the Google auth in production just yet. Cheers, Tom

…

On Wed, 19 Feb 2020 at 14:01, Flavin ***@***.***> wrote: You're keeping all the good stuff for yourselves on a fork? Come on, Tom, merge that stuff back in! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#27?email_source=notifications&email_token=AAIBRFWED2JV6KMCKXHL6Y3RDSOHPA5CNFSM4KXLUKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMGFKVA#issuecomment-588010836>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIBRFSLG5DQMWG4ZMW64M3RDSOHPANCNFSM4KXLUKQA> .

-- *THOMAS G. CLOSE, PHD* Imaging Informatics Officer *Monash Biomedical Imaging* Monash University Room 139, 770 Blackburn Rd Clayton Campus, Clayton VIC 3800 Australia T: +61 3 9902 9804 M: +61 491 141 390 E: [email protected] mbi.monash.edu.au