When you include quotes in your .env file, they actually become part of the string value itself – meaning your application receives the value "localhost" (with quotes) instead of just localhost. This can cause issues with database connection configurations since the quotes are treated as literal characters. Most database drivers and connection libraries expect clean values without quotation marks. That’s why removing the quotes worked for you – it provides the raw value that the database connection expects.

For best practices in .env files, it’s recommended to only use quotes when your values contain spaces or special characters that need to be preserved. For simple values like hostnames, usernames, and ports, you can safely omit the quotes. This approach ensures the values are passed to your application exactly as intended without any extra characters that could interfere with connections or configurations.