blueprint v0.3.2 mix blueprint.plot.msg
Creates a message graph.
mix blueprint.plot.msg [APP] [--colour] [[--lib LIB | --path PATH] ...] [--servers FILE] [-o PATH]
An APP name is provided if the message graph should be
limited to the given application. Otherwise it will be
for the entire blueprint (libraries tracked).
A --colour option can be used to generate a coloured
graph.
A -o option can be used to specify the file to be written.
As many --lib or --path options can be provided to
add additional libraries to the blueprint. If none are
provided, the blueprint will default to using the
libraries found in the project’s build directory.
A --servers option can be used to specify the file to be
used for custom server matching expressions. For more
information see Blueprint.Application.Module. However this
file is expected to be elixir, rather than a string.
## Examples
Generate a graph for the current project:
mix blueprint.plot.msg
Generate a graph for the current project’s example application:
mix blueprint.plot.msg example
Generate a graph for the provided libraries:
mix blueprint.plot.msg --lib example1 --lib example2 --path /example
Generate a graph of mnesia from the standard erlang runtime:
mix blueprint.plot.msg --path $(elixir -e 'IO.puts :code.lib_dir') mnesia
Link to this section Summary
Link to this section Functions
A task needs to implement run which receives
a list of command line args.
Callback implementation for Mix.Task.run/1.