view release on metacpan or  search on metacpan

README  view on Meta::CPAN

Configuration, Data File Locations

    Adenosine creates a few files in either your ${XDG_CONFIG_HOME} and
    ${XDG_DATA_HOME} directory (if your system uses the XDG directory
    standard) or in the ~/.resty directory, otherwise.

 Using Existing, Pre-v2.1 Configuration Files With v2.1

    If you had resty installed before version 2.1 and your system uses the
    XDG config directory standard and you want to continue using your
    existing configuration files, please make a backup of your ~/.resty
    directory and then do:

          $ mkdir -p "${XDG_CONFIG_HOME}/resty" "${XDG_DATA_HOME}/resty"
          $ mv ~/.resty/c "${XDG_DATA_HOME}/resty"
          $ mv ~/.resty/* "${XDG_CONFIG_HOME}/resty"

Request URI Base

    The request URI base is what the eventual URI to which the requests
    will be made is based on. Specifically, it is a URI that may contain

bin/adenosine  view on Meta::CPAN

=head1 Configuration, Data File Locations

Adenosine creates a few files in either your C<${XDG_CONFIG_HOME}> and C<${XDG_DATA_HOME}>
directory (if your system uses the XDG directory standard) or in the F<~/.resty>
directory, otherwise.

=head2 Using Existing, Pre-v2.1 Configuration Files With v2.1

If you had resty installed before version 2.1 and your system uses the XDG
config directory standard and you want to continue using your existing
configuration files, please make a backup of your F<~/.resty> directory
and then do:

      $ mkdir -p "${XDG_CONFIG_HOME}/resty" "${XDG_DATA_HOME}/resty"
      $ mv ~/.resty/c "${XDG_DATA_HOME}/resty"
      $ mv ~/.resty/* "${XDG_CONFIG_HOME}/resty"

=head1 Request URI Base

The request URI base is what the eventual URI to which the requests will be
made is based on. Specifically, it is a URI that may contain the C<*> character