https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36932
Victor Grousset/tuxayo <vic...@tuxayo.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Needs Signoff |Signed Off
--- Comment #7 from Victor Grousset/tuxayo <vic...@tuxayo.net> ---
It works! :)
---
Clarification:
> like someone deploying koha with branches
* with a git repo to be able to use branches
---
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?
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
