faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <sam0x17> compile statically
<FromGitter> <sam0x17> using an alpine docker image
<FromGitter> <sam0x17> not sure if amber bakes all its files tho, or if there are files that need to be on your system for it to work
<FromGitter> <elorest> @waghanza @sam0x17 This is something we've thought about a lot. It's definitely possible to compile all of the assets in using baked file system or just a simple script to read in files as strings and return them when their route is called. Because of the development cycle of most projects and the dynamic nature of many assets we choose not to go this way. Other than assets the environment files might be required but
<FromGitter> ... could be easily over written and compiled in. Environments originally were compiled with the system but we changed this so the CLI and compiled project could read from the same env file.
<FromGitter> <sam0x17> good to know @elorest, I went with the baked file system + static compilation route with github.com/sam0x17/conduit and it worked quite well for me, but I understand the situation
<FromGitter> <waghanza> @elorest what to do both ? compile staticly in `one binary` or `multiple files`
<FromGitter> <waghanza> especially on any *docker* workflow it could be accurate
<FromGitter> <waghanza> I mean *immutable* arch
<FromGitter> <sam0x17> there's also always this approach: https://github.com/sam0x17/s3cmd-shim
<FromGitter> <sam0x17> (you can set up docker so that it will run a CLI effectively in the host by doing some creative stuff with paths and args
<FromGitter> <sam0x17> in particular: https://github.com/sam0x17/s3cmd-shim/blob/master/s3cmd
<FromGitter> <sam0x17> we use that with our devops team members that are on mac ever since s3cmd became semi-permanently broken on macos
<FromGitter> <sam0x17> but the principle applies to any CLI app that you want to have exist in docker, but call from host as if its in the host