view release on metacpan or  search on metacpan

scripts.bare/dex  view on Meta::CPAN

#!/usr/bin/env perl
use warnings;
use strict;
use App::Dex;
use Pod::Usage qw(pod2usage);
use Try::Tiny;

if ( @ARGV && ( $ARGV[0] eq '--help' || $ARGV[0] eq '-h' ) ) {
    pod2usage( -verbose => 2 );
}

my $app = App::Dex->new;

# Throw an error if we couldn't find a config file.
try { $app->config_file } catch { die "Error: No config file found.\n" };

if ( @ARGV ) {
    my $block = $app->resolve_block( [ @ARGV ] );

    if ( ! $block ) {
        if ( $ENV{DEX_FALLBACK_CMD} ) {
            exec $ENV{DEX_FALLBACK_CMD}, @ARGV;
        } else {
            print STDERR "Error: No such command.\n\n";
            $app->display_menu;
            exit -1;
        }
    }

    $app->process_block( $block );
} else {
    $app->display_menu;
}

=pod

=encoding utf8

=head1 NAME

dex - Directory Exec

=head1 DESCRIPTION

B<dex> is a command line utility to simply repeative tasks by defining them in
the specific directory you should be in when running them.

Running dex from a directory with a F<.dex.yaml> or F<dex.yaml> file will
present you with the list of named commands.


 dev                     : Control a local development server.
     start                   : Start a local development server on docker.
     stop                    : Stop a local development server on docker.
     status                  : Show the status of the local development server.
     reset                   : Delete the database volume.
 test                    : Run the tests.


Top level commands have no indentation. Each level of indentation is a child 
command.  For instance you would run C<dex dev start> to trigger 
I<Start a local development server on docker>, but only C<dex test> to trigger 
I<Run the tests>.

=head1 DEX FILE SPEC