App-Zapzi

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

Instead of publishing, if you want to see a copy of an article use
`zapzi show` to view the article in a browser or `zapzi export` to
send a copy of the readable article to the standard output. Both these
commands will not archive the article.

You can chain together adding and showing, eg

    $ zapzi add show README.md

will add a copy of README.md to the database and then open a browser
to show how it looks in readable format.

# Configuration

To view or change configuration variables use the `config get` or
`config set` commands, eg:

    $ zapzi config get                      # to see all set variables
    $ zapzi config get publish_format       # to see one variable
    $ zapzi config set publish_format EPUB  # to set a variable

README.mkdn  view on Meta::CPAN

Instead of publishing, if you want to see a copy of an article use
`zapzi show` to view the article in a browser or `zapzi export` to
send a copy of the readable article to the standard output. Both these
commands will not archive the article.

You can chain together adding and showing, eg

    $ zapzi add show README.md

will add a copy of README.md to the database and then open a browser
to show how it looks in readable format.

# Configuration

To view or change configuration variables use the `config get` or
`config set` commands, eg:

    $ zapzi config get                      # to see all set variables
    $ zapzi config get publish_format       # to see one variable
    $ zapzi config set publish_format EPUB  # to set a variable

bin/zapzi  view on Meta::CPAN

Instead of publishing, if you want to see a copy of an article use
C<zapzi show> to view the article in a browser or C<zapzi export> to
send a copy of the readable article to the standard output. Both these
commands will not archive the article.

You can chain together adding and showing, eg

  $ zapzi add show README.md

will add a copy of README.md to the database and then open a browser
to show how it looks in readable format.

=head1 SUPPORT AND DEVELOPMENT

Bugs and requested issues can be reported at Github. Pull requests are
also very welcome; please try to follow the existing style and
organisation of the module.

  https://github.com/rupertl/app-zapzi/

=head1 FUTURE PLANS



( run in 0.616 second using v1.01-cache-2.11-cpan-64827b87656 )