https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36932
Marcel de Rooy <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |BLOCKED --- Comment #9 from Marcel de Rooy <[email protected]> --- (In reply to Victor Grousset/tuxayo from comment #7) > Not sure about the -dep , it sounds like dependency instead of deployment. > No big deal if nothing else sounds better. > > > --- > > > new param is not documented in the --help > > --- > > > Since it's a safeguard to make sure people don't expose errors info in > production: shouldn't it be the opposite approach? So like a -dev flag that > ktd would have to add in it's startup command line call to koha-plack. > > Wait, here with the current proposal it's very easy to switch back to an > unsafe state: restart plack without putting the flag again. > How do the people in the usecases needing this flag manage the automated > startup of koha on machine boot? > Because that place will need also to not have the -dep forgotten. > > Do we have any setting that we already have to a value for dev envs and > another one for regular prod instances and prod instance using a gittified > setup? (IIUC that's the usecase for this flag). > How do we do it? ENV var that KTD overides and everywhere else it's a prod > oriented value? > koha-conf.xml attribute that the KTD startup replaces with a dev oriented > value so the everywhere else it's a prod oriented value? Coming back a bit later for these things. Since we are in 24.11 now, blocking this one temporarily. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
