Restructure things so that the application is now just another module.

Kohana makes this type of transition fairly straightforward in that
all controllers/helpers/etc are still located in the cascading
filesystem without any extra effort, except that I've temporarily
added a hack to force modules/gallery into the module path.

Rename what's left of "core" to be "application" so that it conforms
more closely to the Kohana standard (basically, just
application/config/config.php which is the minimal thing that you need
in the application directory)

There's still considerable work left to be done here.
This commit is contained in:
Bharat Mediratta
2009-05-27 15:07:27 -07:00
parent 2e285cf3ec
commit 28b41056e3
167 changed files with 2 additions and 1 deletions
@@ -0,0 +1,18 @@
<?php defined("SYSPATH") or die("No direct script access.") ?>
<ul>
<li>
<?= t("Operating System: %operating_system", array("operating_system" => PHP_OS)) ?>
</li>
<li>
<?= t("Apache: %apache_version", array("apache_version" => function_exists("apache_get_version") ? apache_get_version() : t("Unknown"))) ?>
</li>
<li>
<?= t("PHP: %php_version", array("php_version" => phpversion())) ?>
</li>
<li>
<?= t("MySQL: %mysql_version", array("mysql_version" => Database::instance()->query("SELECT version() as v")->current()->v)) ?>
</li>
<li>
<?= t("Server load: %load_average", array("load_average" => $load_average)) ?>
</li>
</ul>