Skip to content

bug: some sites start with release configuration even if passed --debug, some sites don't detect debug mode #16473

Description

@mcdurdin
$ shared-sites/build.sh start
  • ❌ shared-sites: does not detect debug configuration
  • ❓ api.keyman.com: detects --debug and uses (but see bug: local environment detected on k8s deployment api.keyman.com#357)
  • ❌ help.keyman.com: does not detect
  • ✅ keyman.com: detects --debug and uses (but check also that api.keyman.com issue is not present)
  • ✅ keymanweb.com: detects --debug and uses (but check also that api.keyman.com issue is not present)
  • ❌ s.keyman.com: detects --debug but uses 'release' configuration (and vice-versa on production; Dockerfile always uses php.ini-production, this needs to move to init-container.sh, and use the debug-flag-respecting production vs development ini file)
  • ✅ website-local-proxy: detects --debug and uses (not used for deployment, so api.keyman.com issue not relevant)

Activity

added this to the B19S1 milestone on Aug 31, 2026
self-assigned this
on Sep 4, 2026
modified the milestones: B19S1, B19S2 on Sep 12, 2026

mcdurdin commented on Sep 16, 2026

@mcdurdin
MemberAuthor

Closing as resolved: --debug detected consistently on local dev environments on all sites.

moved this from Todo to Done in Keymanon Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

  • Status
    Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions