You'll see in many twilio demo apps

[hasinam2206]

However, keep in mind that this value is only set during the execution of this node.js process, and is only available in child processes spawned by this process. As a general rule, avoid overriding environment variables whenever possible, and instead initialize a configuration variable as shown in the example port. Explicitly load variables from files.env if you're developing on multiple node.

Js projects on the same machine, you may end up with overlapping environment variable names. For example, different messaging applications may need different twilio 11-digit phone number format philippines messaging service sids, but both will be named twilio_message_service_sid. A great way to get project-specific configuration is to use .env. These files allow you to specify a variety of different environment variables and their values.



Typically you don't want to track these files in source control, so when you create one you should add .env to your .gitignore. files .env.example that you can then copy to .env and that will allow you to set the values ​​yourself. A common practice is to have a file .