👉 The world is a funny place, so let's take a look at runtimeconfig.example.conf:
``` # A simple config file that includes some basic settings for our app. runtime: true app: localhost:3000 # This is what happens if you don't include it in your configuration. # You get this error message: runtime: false # And that's a weird way to specify an environment variable, right? env_var: runtime ``` But hey, let's make it even more funny! Here's how we could modify it: ``` # This is the modified file with a few changes for good measure. runtime: true app: localhost:3000 # This should work fine as long as the server doesn't change its address. env_var: runtime # And this one won't be visible in your console output, but it's still valid for debugging purposes. # But remember, running something like this on a production environment is not recommended. # Always test your code thoroughly before deploying to a live application. # And always consider logging any errors or exceptions that might occur during runtime execution. ``` As you can see, modifying the `runtime` option in `env_var`, instead of using it directly, made it something that you could just use as is and didn't have to worry about its validity or location. It's a bit unsettling because it seems like you're intentionally trying to make your life easier but still sticking
