https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39740 --- Comment #29 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Tomás Cohen Arazi (tcohen) from comment #21)
(In reply to Tomás Cohen Arazi (tcohen) from comment #18)
I'd say KTD should set an env flag and we should query for it.
Let me clarify my comment :-D Thanks
I think we should have a `koha-conf.xml` entry or section for this things. I would like to be able to enable stack traces in koha-conf.xml instead of detecting how it is being run.
We could also override using variables which `run.sh` (the startup script KTD uses) could set. This could be useful for running in jenkins where we might want to disable stacktraces for (say) Cypress tasks so they are similar to production, but enable them by default in KTD.
Two koha-conf entries: git_install and test_system. Two (optional) env vars overriding them: GIT_INSTALL and TEST_SYSTEM. Please have a look. Patch 5 includes a few more changes for consistency between koha scripts. -- You are receiving this mail because: You are watching all bug changes.