Ado

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.63 2014-09-09
    - Deleted public/vendor/Semantic-UI.
    - Now example pages depend on Mojolicious::Plugin::SemanticUI,
      but you can just comment 'SemanticUI' in ado.conf and it will not be loaded.
    - Today in 1944 the communists took over Bulgaria.
      As a consequence in 1951 my grand-daddy got bitten and killed by them.
      http://en.wikipedia.org/wiki/Bulgarian_coup_d%27%C3%A9tat_of_1944

0.62 2014-09-07
    - Ado::Plugin: simplified guessing of home_dir and speeded it up.
    - Upgraded to Mojolicious 5.39.
    - Started work on Mojolicious::Plugin::SemanticUI.
      Semantic UI will go there and Ado will depend on this plugin.

0.61 2014-09-01
    - Fixed failing test of crud.pm on Windows.
    - Added example configuration for Hypnotoad in etc/ado.conf.
    - Upgraded to Mojolicious 5.36.
    - Upgraded to Module::Build 0.4210.
    - Upgraded to Email::Address 1.905.

Changes  view on Meta::CPAN

0.60 2014-08-31
    - Upgraded to Mojolicious 5.35.
    - Changed option in Ado::Command::generate::apache2htaccess
      from m|module=s@ to M|modules=s@ and explained the limitation in
      Ado::Command.
    - Fixed failing test on Windows in t/command/adoplugin-01.t.

0.59 2014-08-28
    - Upgraded to Mojolicious 5.33.
    - Improved guessing of 'home_dir', 'lib' and 'templates_root' for CRUD in
      Ado::Command::generate::adoplugin. 'templates_root' defaults to 'templates'.
    - Improved guessing of 'lib' in Ado::Command::generate::crud.
    - Added guessing of templates folder to Ado::Plugin.
      Developing plugins should now be easy!!!
    - $CODENAME changed to
      "Есть" - U+2C05 GLAGOLITIC CAPITAL LETTER YESTU (Ⰵ)
    - Cleanups, test fixes and documentation improvements.
    - Presented Ado at YAPC::EU 2014 in Sofia, Bulgaria on 23 August
      http://act.yapc.eu/ye2014/talk/5652
    - Published presentation on Slideshare:
      http://www.slideshare.net/kberov/ado-yapceu2014
    - Improved Ado::Sessions::File.

lib/Ado.pm  view on Meta::CPAN

=head2 CODENAME

Returns the current C<CODENAME>.

=head2 home

    #/where/is/your_app/rootdir
    $app->home;

Returns the root directory into which $app is installed.  The guessing order is
the following:

=over

=item 1. If C<$ENV{MOJO_HOME}> is defined, it is honored.

=item 2. The upper directory of the directory in which the starting executable
C<$app-E<gt>moniker> is found, e.g. C<bin/..>.  This may happen to be the same
as L</ado_home>.

lib/Ado/Command/generate/apache2vhost.pm  view on Meta::CPAN

See also documentation for Apache2 directive DocumentRoot.

=head2 c|config_file=s

Full path to the file in which the configuration will be written.
If not provided the configuration is printed to the screen.

=head2 s|with_suexec

Adds C<SuexecUserGroup> directive which is effective only
if C<mod_suexec> is loaded. The user and the group are guessed from the
user running the command.

=head3 u|user=s

User to be used with suexec.

=head3 g|group=s

Group to be used with suexec.

lib/Ado/Manual/Contributing.pod  view on Meta::CPAN

Use L<DBIx::Simple::Class>.
Generate your classes from tables using C<dsc_dump_schema.pl> utility
that comes with DBIx::Simple::Class.
Feel free to contribute to L<DBIx::Simple::Class>.
Minimize SQL complexity. Write ANSI SQL if you need to write SQL.
Write your SQL in a way to be compatible with
L<SQLite|http://sqlite.org/>, L<MySQL|http://dev.mysql.com/>
and L<PostgreSQL|http://www.postgresql.org/>.
Use the L<DBIx::Simple::Class/SQL> feature to achieve this.
See L<DBIx::Simple::Class/SQL> and its source to figure out how to do it.
To guess the current driver:

  use DBI::Const::GetInfoType;
  #...
  my $dbms = $self->dbh->get_info( $GetInfoType{SQL_DBMS_NAME} );
  if($dbms eq 'SQLite'){
  ...
  }

=head2 PLUGINS

lib/Ado/Plugin.pm  view on Meta::CPAN

Extension used for the plugin specific configuration file. defaults to 'conf';

  my $ext  = $self->ext;

=head2 home_dir

  my $plugin_home = $self->home_dir;

The plugin base directory.
This path works both while developing a plugin and after installing the plugin.
Using the guessed value allows you to have Ado plugins installed at arbitrary paths,
possibly not the same where Ado is installed.
As noted elsewhere, Ado plugins can be distributed as separate Ado applications and used
together with other plugins to create custom enterprise-grade systems.

=head2 name

The name - only the last word of the plugin's package name.

  $self->name # MyPlugin

lib/Ado/Plugin/I18n.pm  view on Meta::CPAN

sub register {
    my ($self, $app, $config) = shift->initialise(@_);

    #Make sure we have all we need from config files.
    $config->{default_language} ||= 'en';

    #Supported languages by this system
    $config->{languages} ||= ['en', 'de', 'bg'];

    # Language will be guessed from one of these places in the order below.
    # Specify/narrow your preferences in etc/plugins/i18n.conf.
    $config->{language_from_route}   //= 1;
    $config->{language_from_host}    //= 1;
    $config->{language_from_param}   //= 1;
    $config->{language_from_cookie}  //= 1;
    $config->{language_from_headers} //= 1;
    $config->{language_param}        //= 'language';

    #Allow other namespaces too
    $config->{namespace} ||= 'Ado::I18n';