view release on metacpan or  search on metacpan

README.mkdn  view on Meta::CPAN

Task runner heavily inspired by Task ([https://github.com/go-task/task](https://github.com/go-task/task)).
Basically, I wanted `Task`, but with a `foreach` construct.

See `perldoc App::DoThe` for the syntax of the `Dothe.yml` file.

# DOTHE SYNTAX

The configuration file is in YAML. It follows, by and large, the
format used by Task.

By default, \`dothe\` looks for the file \`Dothe.yml\`.

Where entries can be templates, they are evaluated via [Text::Template](https://metacpan.org/pod/Text::Template).
Basically, that means that in a template all that is surrounded by double curley braces
is evaluated as Perl code. Those code snippets are evaluated within the
`App::Dothe::Sandbox` namespace, and have all the `vars` variables
accessible to them.

## `code` section

Takes an array. Each item will be eval'ed in the namespace

lib/App/Dothe.pm  view on Meta::CPAN

Task runner heavily inspired by Task (L<https://github.com/go-task/task>).
Basically, I wanted C<Task>, but with a C<foreach> construct.

See C<perldoc App::DoThe> for the syntax of the F<Dothe.yml> file.

=head1 DOTHE SYNTAX

The configuration file is in YAML. It follows, by and large, the
format used by Task.

By default, `dothe` looks for the file `Dothe.yml`.

Where entries can be templates, they are evaluated via L<Text::Template>.
Basically, that means that in a template all that is surrounded by double curley braces
is evaluated as Perl code. Those code snippets are evaluated within the
C<App::Dothe::Sandbox> namespace, and have all the C<vars> variables
accessible to them.

=head2 C<code> section

Takes an array. Each item will be eval'ed in the namespace