.env not included in the app build

[seve-andre]

I'm building an app using Diesel + MySQL, and the Getting Started recommends to create a .env file with the DATABASE_URL. Mine looks something like this:

DATABASE_URL=mysql://mitch:password@localhost/db_name

Everything looks good when using pnpm tauri dev and pnpm tauri build, but after installing the .deb package and running the app, an error shows up:

thread 'tokio-runtime-worker' panicked at 'DATABASE_URL must be set: NotPresent', src/db.rs:11:49
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

So, I'm guessing the .env file is not included in the build, but how could I solve this?

[FabianLars]

You potentially could bundle it as a resource, but i think this would not be next to the binary in a .deb package.

Also keep in mind that shipping .env files is often not the best idea since then all your users can just read the URL including the password.
If you don't care about that you could look at https://docs.rs/dotenvy_macro/0.15.7/dotenvy_macro/ which will include the env var from the .env file into the binary at build time (still somewhat easy to read but at least not a plain text file)

[Shubh-81]

If not shipping .env, then what is a good way to handle environment variables in built binaries?

[developermindsetcom]

Here's a youtube tutorial on 6 different ways how you can get environment variables set in Tauri, including .env files:
https://youtu.be/eFRl38t-D1U