Statics are ignored

[FrequentFlyer]

@Zane_Milakovic

I tried using the [build.args] element within the fly.toml , but that does not seem to be respected. In the shell output I can not see the build command to validate.

I don’t believe you need a project.toml.
It can all be contained in the fly.toml itself, but with the right syntax, etc.
Here are two separate links to the doco, specifically the build section related bits.

So it’ll be something like:

[build]
  builder = "paketobuildpacks/builder:base"
  buildpacks = ["gcr.io/paketo-buildpacks/go"]
  [build.args]
    BP_KEEP_FILES = "public/*"

You may need a / or ./ in front of the public/* there.

In the shell output I can not see the build command to validate.

You could do $LOG_LEVEL=debug flyctl deploy ... to get more info on what’s going on.

I can’t see a way to define ENV variable to be used on the builder in the fly.toml

ENV variables are only available for use at run-time, and are setup via fly secrets.
For build-time arguments, the two links above will help.

And you are not allowed to redeploy the builder.

Quoting an answer from an employee:

@jerome

Every organization has its own builder. They come with a 50GB volume.

The easiest way to fix the issue is to destroy your builder. Find the name of your builder for the organization that owns the app you’re building by looking for an app that starts with fly-builder- and destroy it with flyctl apps destroy fly-builder-xyz . The next build will create a new builder with a fresh volume.

Are my choices creating a Docker file (go-repo example is 2 years old), or creating my own build pack, that I fully don’t understand?

It appears that using the Dockerfile is what you have to do if you want to serve static files (that you can make available in your final Docker image).

Creating your own buildpack is not necessary, I think.
Just need to pass the build args right.
I hope the above links will help get you going