You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether you're using git-ops, want to version your Dockerfiles in source control, or just want to store them in a file, Kuby should support emitting them via the CLI. Perhaps something like kuby dockerfiles -o /path/to/output_dir.
The text was updated successfully, but these errors were encountered:
It turned out to be important to separate the dockerfiles for me. So you'll see in the script linked above, I call for the main dockerfile and the assets dockerfile separately. Because of the way this works, there is a new codepath that executes when building the assets-only file, (and it was a while ago already that I did this, but I remember finding out it can fail separately.)
Nice, that's great :) The --only option does make this easier now. Still would be nice to have a CLI option for this, although Kuby would have to impose some sort of file naming convention like you've done with the .assets suffix.
Whether you're using git-ops, want to version your Dockerfiles in source control, or just want to store them in a file, Kuby should support emitting them via the CLI. Perhaps something like
kuby dockerfiles -o /path/to/output_dir
.The text was updated successfully, but these errors were encountered: