You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the server works in a simple way, import the .env and use it. But it doesn't have a hardy configuration, for example: what happens if I try to run the server and not import the needed .env?, the server isn't prepared for this and will crash without leaving a suitable error message to track the error.
That's the reason why we should add a separate logic for the server configuration before starting it, initializing the needed variables, handling the errors properly, and adding other needed configurations that currently we don't have, for example, to change the address or the development/production ports
Criteria acceptance
The server knows what should do if don't have the required .env
The server is importing carefully the configuration and is handling errors
The text was updated successfully, but these errors were encountered:
Currently, the server works in a simple way, import the .env and use it. But it doesn't have a hardy configuration, for example: what happens if I try to run the server and not import the needed .env?, the server isn't prepared for this and will crash without leaving a suitable error message to track the error.
That's the reason why we should add a separate logic for the server configuration before starting it, initializing the needed variables, handling the errors properly, and adding other needed configurations that currently we don't have, for example, to change the address or the development/production ports
Criteria acceptance
The text was updated successfully, but these errors were encountered: