Feature: automatic .env reading

[vanodevium]

golang can read .env
so it would be nice to have ability automatic reading .env from cwd

[yassinebenaid]

Nice suggestion 🔥 . I would love to see this in bunster .

The implementation design would be to have a builtin that automatically loads from a file:

Example:

# load from a file
envload file.env

# loads from file named .env
envload 

what do you think

[vanodevium]

@yassinebenaid
Nice. Also it can be useful as build parameter:

bunster build --envload

[yassinebenaid]

What I understand from your suggestion is the following:

1. you build a program like this:

bunster build script --envload

2. the compiler will automaticaly read from .env and embeds the values into the binary.
3. The variables will be available as variables at runtime.

Correct me if I'm wrong !

[vanodevium]

I have to correct you

I want to load variables from .env (or other naming) when I run already built binary.

Lets imagine: I build binary and push it to the remote host.

So, if there would be .env file in folder, where i launch binary, it will try to read and parse that .env and use variables in runtime.

few word about build parameter

bunster build script --envload: this variant will be try to read .env file
bunster build script --envload=foo.bar: this variant will be try to read foo.bar file

[yassinebenaid]

Ammm, I wonder why would you prefer that over using the envload command. Apparently, it's the same with two different methods.

I mean, if both methods do the same thing, why don't we just keep one of them. I vote for first one.

The envload is going to be builtin command, you don't need any external program. Also, It will allow you to do a lot of tricks. such as:

# in condition
if true; then
    envload   
fi

# in sub-shell
(
     envload   
)

# ...

[vanodevium]

@yassinebenaid Sounds good. Ok.

[vanodevium]

@yassinebenaid But don't forget support custom file naming, not only .env, please

[yassinebenaid]

don't forget support custom file naming, not only .env

Yep, sure.

It'll be added soon in a future release.