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
Burp currently has a composition that takes the main-dependency wherein services are written as either the main application or one of the dependencies, this works well with simpler applications, but for applications that require building one or more applications from a source, this falls apart.
As such, a new composition proposal needs to be implemented and this approach is the 'services' approach wherein all applications are regarded as a service and neither is considered the main application. In this approach, we create a schema as follows:
To support this change, the environment.override will be removed and .env files will be merged into one separated by a comment that will signify to the processor of a new .env file such as in the example:
In addition, future versions of the composition should support more file formats such as json, yaml instead of limiting towards toml which will help with how developers handle their preferences, for example, with JSON:
In addition to the above, flags can be added to specify a specific mode in the application such as:
flags = ["parallel.builds"]
parallel.builds enables the Burp client to build the images not in a synchronous manner, but in parallel, so if you have more than one services that require an image to be built, Burp will build them in parallel and then spawn the necessary containers.
Burp currently has a composition that takes the main-dependency wherein services are written as either the main application or one of the dependencies, this works well with simpler applications, but for applications that require building one or more applications from a source, this falls apart.
As such, a new composition proposal needs to be implemented and this approach is the 'services' approach wherein all applications are regarded as a service and neither is considered the main application. In this approach, we create a schema as follows:
To support this change, the
environment.override
will be removed and.env
files will be merged into one separated by a comment that will signify to the processor of a new.env
file such as in the example:In addition, future versions of the composition should support more file formats such as
json
,yaml
instead of limiting towardstoml
which will help with how developers handle their preferences, for example, with JSON:The text was updated successfully, but these errors were encountered: