Need a way to have multiple Zestfiles, and therefore multiple services, built from the same root context.
Problem:
Zest commands are hardcoded to look for ./Zestfile, they could be changed to take an optional argument or flag, except zest all runs zest commands everywhere if finds a Zestfile with no arguments. The all command also wouldn't be able to identify services to build if the Zestfile was named any other way.
Maybe make zest look for Zestfile.* as well, but already using Zestfile.example as a way of deactivating a Zestfile, so will have to change that to Zestfile-example
Need a way to have multiple Zestfiles, and therefore multiple services, built from the same root context.
Problem: Zest commands are hardcoded to look for
./Zestfile
, they could be changed to take an optional argument or flag, exceptzest all
runs zest commands everywhere if finds aZestfile
with no arguments. The all command also wouldn't be able to identify services to build if theZestfile
was named any other way.Maybe make zest look for
Zestfile.*
as well, but already usingZestfile.example
as a way of deactivating a Zestfile, so will have to change that toZestfile-example