Cognito redirect ur ls configurable

[stevbark]

Should fix the redirect issue when we update the URL value in AWS.

[paulespinosa]

A more descriptive name would help me understand the purpose of this variable.

[ju1es]

+1

[paulespinosa]

This change is for Issue #503, right?

[stevbark]

This change is for Issue #503, right?

yes. #503

[ju1es]

sorry in advance if I'm not understanding this correctly! but what's the purpose of .env.example ? if it's the .env that will run in production ('.env.example' then is a bit misleading), i think we'd specify environment variables in the docker file right? I started cooking up a config system that'll generate at runtime,

https://github.com/hackforla/HomeUniteUs/pull/527/files

maybe we add this there?

[paulespinosa]

@ju1es

but what's the purpose of .env.example ?

My understanding is that it's a file that we can check into version control (git) to demonstrate the environment variables that need to be set within an deployment environment without the actual values (secrets). Different environments (local dev, qa, stage, prod) should have different values.

i think we'd specify environment variables in the docker file right?

If the .env file exists when building the docker image, it will be pulled into the docker image and used by the application when it starts up. I imagine the prod version of the .env file is stored somewhere in AWS that the continuous integration build can access. The CI process is something I'm not familiar with yet, though.

[stevbark]

New changes pushed. more descriptive name added.