Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename the public test environments #2221

Open
vohmar opened this issue Nov 24, 2021 · 3 comments
Open

Rename the public test environments #2221

vohmar opened this issue Nov 24, 2021 · 3 comments

Comments

@vohmar
Copy link
Contributor

vohmar commented Nov 24, 2021

To reduce confusion lets rename the public test environemets to demo. This way if we talk about test env we always mean the environemnts for automated testing and demo is the publicly available environment for pre-production testing, practice and feature reviews

@yulgolem
Copy link
Contributor

yulgolem commented Nov 24, 2021

Actually I strongly advise against it.
That's a common naming practice in rails applications.
Renaming test envirnonent might not only confuse future app developers alot, but also may break not just our app, - it might break any of the used gems (since they could have checks involving current environment). Than could have bigger impact and be more confusing then simple renaming of Git branches from master to main for the sake of BLM/SJW.

I think it might be wisier to use public test or pre-production term to the public test environment.

@vohmar
Copy link
Contributor Author

vohmar commented Nov 24, 2021

well i must admins its strange choice to use such an ambiguous naming for automated testing environments,. So we will flip the task the other way around and rename our own public test to something like demo or pre-production. thank you for your feedback @yulgolem

@vohmar vohmar changed the title Rename the env for running automated tests Rename the public test environments Nov 24, 2021
@OlegPhenomenon
Copy link
Contributor

@vohmar How I understand we have production test environment? Is this ticket still actual? Can it be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants