Closed seland closed 6 years ago
We have a flag in the .env
file for production. If false
we can enable the debug tools. @seland how would you include it so that people like @mimetic can easily access it?
I don't know who is @mimetic
Em 24 de jan de 2018 8:30 PM, "Florian Lenz" notifications@github.com escreveu:
We have a flag in the .env file for production. If false we can enable the debug tools. @seland https://github.com/seland how would you include it so that people like @mimetic https://github.com/mimetic can easily access it?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Bit-Nation/BITNATION-Pangea-mobile/issues/97#issuecomment-360296027, or mute the thread https://github.com/notifications/unsubscribe-auth/AiFx52Oha7XeYXECR7hwVv-9ug0AwJgoks5tN68JgaJpZM4Rraiq .
@florianlenz Do we use PRODUCTION=true for releases only? I mean, can we have it set to false on CI builds?
Feature / Issue
Testers need to use some helper features that is not supposed to be included in production build. We need to implement feature toggle for that. Discussion point is where should flag for toggle come from. Suggestion is that - use some special action to activate testing mode and use some flag from .env to allow that action to activate testing mode. That way tester can see the build as it is for production and also can use helpers if needed.
Acceptance criteria
Additional information
It's preferred to be able to use 'testing mode' on every CI builds.