Include config file as part of app binary

[sidoki]

Description

In order to provide deployment consistency, we need to include configuration files as part of the application binary, especially during app deployment to avoid unintented changes made from the config file if copied manually.

To Reproduce

Currently we need to copy paste the app binary and config files separately.

Expected Behavior

When building the app, the configuration files will be included as part of the binary. Hence, the user just need to copy the binary to deployment env.

Environment:

Additional Context

[kaplanelad]

Consideration of the issue led me to the following proposal:

• Create a new configuration file named imbede.yaml, for example.
  The YAML should be like this:

development:
   ....
production:
  ....
custom-env:
  ....

• During the build process, load this file if it exists at a cost.
• At the runtime, if Loco builds with imbede.yaml points the configuration only to this file content

@jondot any other thoughts?

[tjyang]

For my understanding, This request is more like this one at rust-cli/config-rs#408
End goal is to have myapp2-cli has at least config/production.yaml and and some files under frontend/* embeded inside the binary.

[me@rocky9t01a myapp2]$ tree -L 2
.
<snipped>
├── config
│   ├── development.yaml
│   ├── production.yaml
│   └── test.yaml
├── db.sqlite
├── examples
│   └── playground.rs
├── frontend
│   ├── dist
│   ├── favicon.ico
│   ├── index.html
│   ├── package.json
│   ├── pnpm-lock.yaml
│   ├── README.md
│   ├── src
│   └── vite.config.js
<snipped>

20 directories, 20 files
[me@rocky9t01a myapp2]$

[jondot]

@jurukode i'm not sure about config files being embedded yet, because they are config files -- they are supposed to be changed/tweaked/etc.

I believe your pain point is a single "deliverable", which you can get with a docker container.

Just to reiterate -- I think embedding is cool, but i'm not sure its what most people would expect.