Working with Assets

Bonfire considers any CSS files, javascript files, and many image files to be Assets. While we understand that projects will often contain Flash files or other types of files that would be considered 'assets', Bonfire only accounts for these three types of files but does provide some helper methods to assist with other types of files.

Assets files can be stored in an application-wide repository, in your theme, or with each module. Because of the possibility of some of these files not being web-accessible, module-related assets are always combined and cached in a web-accessible folder.

Assets can be located in one of several locations:

/bonfire/modules/my_module/assets
/public/themes/active_theme/assets
/public/themes/default_theme/assets
/public/assets

Whenever you use one of the asset rendering methods, like css(), js(), and image(), it will search in each of those folders (as well as a folder named by the asset type under those folders, ie. 'css') in the order listed above. Note that it only looks within the module if it was added via add_module_css() or add_module_js().

Customizing Asset Base Folder

If you need to, you can customize the folders that your assets are located in via settings in the /application/config/application.php configuration file.

To change the primary folder that all of your assets are located in, you can set the 'base' key in the assets.directories setting.
Note that this is not recommended as it may cause instability in the application.
Testing has not been done to ensure that this is a viable option at the moment.

$config['assets.directories'] = array(
    'base'   => 'assets',
    'cache'  => 'cache',
    'css'    => 'css',
    'image'  => 'images',
    'js'     => 'js',
    'module' => 'module',
);

Customizing Asset Folders

Within the base folder (above), each asset is organized by asset type.
By default, the folders are named js, css, and images.
This can be changed in the assets.directories setting in the application config file.
Again, though this has not been tested to ensure this works.
Changing this value might render your site unusable.

$config['assets.directories'] = array(
    'base'   => 'assets',
    'cache'  => 'cache',
    'css'    => 'css',
    'image'  => 'images',
    'js'     => 'js',
    'module' => 'module',
);

Working With CSS

Stylesheets can be hosted with the application or on other servers.
However, when it comes time to tweak your site's front-end performance, only those files that are hosted locally with the site can be combined and minified successfully.
It is recommended that you always use the raw stylesheets (not minified) to take full advantage of the minification abilities, as minifying a CSS file twice might corrupt the styles.

css()

This method provides a simple way to render all of your CSS links in one method call.
It can be used in two different fashions: to output a single link tag, or to output link tags to all stylesheets that it knows about.

Whenever a relative path is provided, it is assumed to be relative to either the main folder being searched in (i.e. /public/assets) or the type-specific folder (e.g. /public/assets/css).

When called with no parameters, the css() method will create links for all stylesheets that have been added to it via either the add_css() or add_module_css() methods, below.

Assets::css();

// Creates:
<link rel="stylesheet" type="text/css" href="http://mysite.com/themes/default/screen.css" media="screen" />

Media Type

You can specify the media type for your CSS to render, by passing it as the second parameter.
The default value is 'screen'.

Assets::css(null, 'screen');

Bypassing Inheritance

Bonfire's Assets system is designed with a Parent/Child theme framework in mind.
That means that you can quickly build a new theme that inherits all of a default (or parent) theme and only changing the files that need to be changed.
This applies to both assets and layout files.

If you're using a theme that you've created called 'darthvader', it will look for files of the same name in both the darthvader theme and the default theme.
If you do not want it to look for and include these files, you can pass in TRUE as the third parameter.

Assets::css(null, 'screen', TRUE);

Global Files

A couple of different files will automatically appear within your styles, without you needing to do any work.

The Assets library will search for a file within your theme for a file named the same as the media that you're currently rendering.
By default, this is the public/themes/my_theme/screen.css file.

It will also look for any stylesheets within your theme that match the name of the controller that is active.
So, if the blog controller is currently running, it will look for a file at public/themes/my_theme/blog.css.

Rendering a Single File

When you just want to output a link to a single CSS file, you can use the css() method with a single parameter that is the name of the file to link to.
The link can be either relative or absolute.

echo Assets::css('http://mysite.com/path/to/my.css');
// Output: <link rel="stylesheet" type="text/css" href="http://mysite.com/path/to/my.css" media="screen" />

echo Assets::css('/path/to/my.css');
// Output: <link rel="stylesheet" type="text/css" href="http://mysite.com/path/to/my.css" media="screen" />

Rendering Multiple Custom Files

If you want to render multiple links to CSS files, you can pass an array of stylesheets.
These stylesheets will be merged with any styles that have been previously added via either add_css() or add_module_css().

$styles = array(
    'bootstrap.css',
    'markitup/sets/minimal/styles'
);

Assets::css($styles);

add_css()

Adds additional file(s) to the links that are output with the css() method.
The first parameters is the name of the file to be linked to.
It should be relative to one of the paths described above.
The second, optional, parameter is the media type.
This defaults to 'screen'.

Assets::add_css('blog.css');

add_module_css()

Adds a stylesheet that is part of a module to the styles to be output with the css() method.
The first parameter is the name of the module.
The second is the name of the file to be linked to.
The third, optional, parameter is the media type this file belongs to.
It defaults to 'screen'.

Assets::add_module_css('blog', 'posts.css');

Because module files are often inaccessible via a web browser, all module files are combined and cached in the public/assets/cache folder.
The name of the file is built as follows for the maximum reuse:

{theme name}_{module name}_{controller name}_mod.css

The above blog/posts.css file would be in a file named default_blog_blog_mod.css.

Working With Javascript

Script files can be hosted with the application or on other servers.
However, when it comes time to tweak your site's front-end performance, only those files that are hosted locally with the site can be combined and minified successfully.
It is recommended that you always use the raw scripts (not minified) to take full advantage of the minification abilities, as minifying a JS file twice might corrupt the script.

For the sake of the Assets library, javascript files are broken up into 3 types of scripts:

  • External scripts are javascript files that included with a <script src=""></script> tag. These will typically be hosted with your site, but might be hosted on another server.
  • Inline scripts are scripts that are intended to be written out as part of the page's HTML. You may include a file as inline for performance reasons or simply because it only affects a single page on your site and including it in a larger external file does not make sense.
  • Module scripts are scripts that are part of a module within Bonfire. Because of security reasons, you often will not be to access the module files from the browser so these scripts are always combined and cached in the main assets/ folder.

js()

This method provides a single call to render all external, module, or inline script tags.

Whenever a relative path is provided, it is assumed to be relative to either the main folder being searched in (i.e. /public/assets) or the type-specific folder (e.g. /public/assets/js).

When called with no parameters, the js() method will create links/inline-code for all scripts that it knows about.

echo Assets::js();

Might produce:

<script src="http://bonfire.dev/assets/js/bootstrap.min.js" type="text/javascript" ></script>
<script type="text/javascript">
$(document).ready(function(){
    $(".dropdown-toggle").dropdown();$(".tooltips").tooltip();$(".login-btn").click(function(e){ e.preventDefault(); $("#modal-login").modal(); });
});
</script>

Notice that the inline scripts are automatically wrapped with customizable open and close strings.
In this case, it produced an appropriate wrapper for use with jQuery.
This can be changed in the application/config/application.php file.

$config['assets.js_opener'] = '$(document).ready(function(){'. "\n";
$config['assets.js_closer'] = '});'. "\n";

Single Script Tags

If you pass the name of a script file as the first parameter, then it will output a link to only that file.
Note that if it cannot find the script in any of the standard locations, it will not create a link for it.

echo Assets::js('some_script.js');

Adding Scripts while Rendering

You can pass an array of script files as the first parameter of the script and they will be added to the scripts to be linked to.
The function will then proceedd as if you had not passed any parameters in, creating links for all external, inline, and module scripts, including the ones that you did actually pass in.
An optional second parameter allows you to specify whether the scripts are 'external' or 'inline';

echo Assets::js( array('script1.js', 'script2.js'), 'inline' );

external_js()

This method creates the links for all external scripts that it knows about.
This is called automatically by the js() method and does not need to be called again if you are using that method.

You can pass either an array of scripts or a single script as the first parameter and only those script files will have links created for them.

If you are using a JS loader, like head.js, you might need a list of files instead of links created.
You can get this by passing true as the second parameter.

echo Assets::external_js(array('script1.js', 'script2.js'), true);

// Produces
"http://mysite.com/assets/js/script1.js", "http://mysite.com/assets/js/script2.js"

By default, the Assets library will ensure that all files have a .js file extension.
If you have some files have a different extension, you can pass false as the third parameter.

inline_js()

Handles the inline script creation for the js() method.
You do not need to call this script by itself when using that method.

module_js()

Returns a link to a combined file that includes any scripts added with the add_module_js() method, below.
When this method is called, all files are combined into a single file that is cached in the primary public/assets/cache folder.

You can affect how the file is named as well as minification of the new file, via options that are discussed in Section 5, below.

Working With Images

With mobile/desktop development becoming so prevalent, you often need a simple method to get an image that is only as big as you need it to be, smaller for mobile browsers and larger for desktops.
With responsive design, you can fine-tune the bandwidth that your site's images are consuming even further based on the width of the browser window.

Bonfire's image controller provides simple, on-the-fly creation of resized images.
This is available at:

http://mysite.com/images

Image Size and Cropping

To return a square thumbnail of a large photo, you can choose to let the images library automatically crop the photo for you, while creating a thumbnail image.
Pass along a size parameter that will define how wide and how tall the image should be.

<a href="http://mysite.com/images?size=80">My Thumbnail</a>

If you prefer to set a specific height and width, in pixels, for the image, you can use the height and width params to the url.

<a href="http://mysite.com/images?height=60&width=100">My Thumbnail</a>

You can also simply pass a width or height params to intelligently resize the image.
Whichever param is passed will determine which is the "master" param.
ex. If height is passed, the image will resize to a height of 60 and whatever width maintains aspect-ratio.

<a href="http://mysite.com/images?height=60">

By default, Bonfire will scale your image to fit within the new image size.
To resize the image and disregard aspect-ratio, pass along a ratio=no parameter.

<a href="http://mysite.com/images?size=80&ratio=no">My Thumbnail</a>

Image File Path

Bonfire will look for the images within the public/assets/images folder in your web root.
If you need to pull files from a different folder, you can use the assets parameter and pass in a folder relative to the webroot.

<a href="http://mysite.com/images?size=80&assets=assets/images">My Thumbnail</a>

Module Images

If you have images stored in a specific module you can access those images by passing the module name to the module parameter.

<a href="http://mysite.com/images/image=name.png?module=blog">Blog Image</a>

This will load an image in the assets/images folder in the blog module: /application/modules/blog/assets/images/image-name.png

Boosting Performance

Large strides have been made over the last few years in recognizing techniques to help boost your client-side performance, or apparent performance to make it feel to the user like your site is loading faster.
Bonfire provides a couple of different tools to help you with that.

Combining Assets Into Fewer Files

The first step to take usually involves combining your CSS and javascript files into as few files as possible to reduce the number of HTTP connections needed, since these are relatively slow.

You can turn on combining files in your application/config/application.php configuration file.
It is recommended to turn off combining in your development environment but turn it on in testing and production environments.

$config['assets.combine'] = true;

This will create 2 files that are cached within the public/assets/cache folder.
The first file combines all external files that are hosted within this site into a single file.
The second file contains all of your module-specific files.
This is the same file that is always generated for module js and css files.

Combining works for both CSS and Javascript files.

Minimizing Assets

In addition to just combining the files, you can minimize your CSS and Javascript files, reducing the amount of bandwidth used for every page.
You can turn on minizing files in your application/config/application.php configuration file.
It is recommended to turn off minimizing in your development environment but turn it on in testing and production environments.

$config['assets.js_minify'] = true;
$config['assets.css_minify'] = true;

Encrypting File Names

While not a performance booster, those more security-conscious developers might dislike the typical naming convention of your cached asset files which display limited amount of information about the controller and module running.
To obscure this information you can turn on file name encryption.
This creates an md5 hash of the normal file name to cache the file as.

$config['assets.encrypt_name'] = true;

Clearing the Asset Cache

You can delete all of your asset's cached files by calling the clear_cache() method.
ALL cached assets will be deleted.

Assets::clear_cache();

Helper Functions

Three helper functions are provided to help create manual links to assets within your view files.

assets_path()

This returns a full URI to the main asset folder.

echo assets_path();

// Produces
http://mysite.com/assets/

css_path()

This returns a full URI to the CSS folder.

echo css_path();

// Produces
http://mysite.com/assets/css/

js_path()

This returns a full URI to the scripts folder.

echo js_path();

// Produces
http://mysite.com/assets/js/

img_path()

This returns a full URI to the images folder.

echo img_path();

// Produces
http://mysite.com/assets/images/
Profiler
Profiler Console 0 Load Time 13.6ms Memory Used 1.11 MB Database 4 Queries vars & Config Files 87

Console

Memory Usage

Benchmarks

1 ms Loading Time: Base Classes
10 ms Controller Execution Time ( Docs / Index )
14 ms Total Execution Time

Queries

0.0002 SELECT GET_LOCK('9262f7fd73d9d4ec03e5ee029420f264256bd118', 300) AS ci_session_lockSpeed: 0.0002 - Possible keys: - Key Used: - Type: - Rows: - Extra: No tables used
0.0003 SELECT `data` FROM `bf_ci3_sessions` WHERE `id` = '9262f7fd73d9d4ec03e5ee029420f264256bd118'Speed: 0.0003 - Possible keys: - Key Used: - Type: - Rows: - Extra: no matching row IN const table
0.0003 SHOW TABLES FROM `remytek`
0.0002 SELECT * FROM `bf_settings`Speed: 0.0002 - Possible keys: - Key Used: - Type: ALL - Rows: 37 - Extra:
0.0010 Total Query Execution Time

Session User Data

__ci_last_regenerate 1532013216
requested_page http://remytek.com/index.php/docs/developer/working_with_assets
previous_page http://remytek.com/index.php/docs/developer/working_with_assets

GET DATA

No GET data exists

POST DATA

No POST data exists

URI STRING

docs/developer/working_with_assets

CLASS/METHOD

docs/index

HTTP HEADERS

HTTP_ACCEPT text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
HTTP_USER_AGENT CCBot/2.0 (http://commoncrawl.org/faq/)
HTTP_CONNECTION close
SERVER_PORT 80
SERVER_NAME remytek.com
REMOTE_ADDR 54.225.32.164
SERVER_SOFTWARE Apache/2.4.18 (Ubuntu)
HTTP_ACCEPT_LANGUAGE
SCRIPT_NAME /index.php
REQUEST_METHOD GET
HTTP_HOST
REMOTE_HOST
CONTENT_TYPE
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
HTTP_ACCEPT_ENCODING x-gzip, gzip, deflate
HTTP_X_FORWARDED_FOR

CONFIG VARIABLES

base_url http://remytek.com/
index_page index.php
uri_protocol AUTO
url_suffix
language english
charset UTF-8
enable_hooks true
subclass_prefix MY_
composer_autoload false
permitted_uri_chars a-z 0-9~%.:_-
allow_get_array true
enable_query_strings false
controller_trigger c
function_trigger m
directory_trigger d
log_threshold 0
log_path /var/www/clients/client2/web2/bonfire/application/logs/
log_file_extension
log_file_permissions 420
log_date_format Y-m-d H:i:s
error_views_path
cache_path /var/www/clients/client2/web2/bonfire/application/cache/
cache_query_string false
encryption_key a9ff89765e5fc8a4ee203140cfff9400
sess_cookie_name bf_session
sess_expiration 7200
sess_time_to_update 300
sess_match_ip false
sess_expire_on_close false
sess_encrypt_cookie false
sess_use_database false
sess_table_name sessions
sess_match_useragent true
sess_driver database
sess_regenerate_destroy false
sess_save_path ci3_sessions
cookie_prefix
cookie_domain
cookie_path /
cookie_secure false
cookie_httponly false
standardize_newlines false
global_xss_filtering false
csrf_protection true
csrf_token_name ci_csrf_token
csrf_cookie_name ci_csrf_token
csrf_expire 7200
csrf_regenerate true
csrf_exclude_uris Array ( )
compress_output false
time_reference utc
rewrite_short_tags false
proxy_ips
bonfire.installed 1
site.default_user_timezone UM8
modules_locations Array ( [/var/www/clients/client2/web2/bonfire/application/modules/] =&gt; ../../application/modules/ [/var/www/clients/client2/web2/bonfire/bonfire/modules/] =&gt; ../../bonfire/modules/ )
site.backup_folder archives/
contexts Array ( [0] =&gt; content [1] =&gt; reports [2] =&gt; settings [3] =&gt; developer )
enable_activity_logging true
sparks_path ../sparks/
template.site_path /var/www/clients/client2/web2/web/
template.theme_paths Array ( [0] =&gt; themes )
template.default_layout index
template.ajax_layout ajax
template.use_mobile_themes false
template.default_theme default/
template.admin_theme admin
template.message_template &lt;div class=&quot;alert alert-{type} alert-dismissable&quot;&gt; &lt;button type=&quot;button&quot; class=&quot;close&quot; data-dismiss=&quot;alert&quot; aria-hidden=&quot;true&quot;&gt;&amp;times;&lt;/button&gt; &lt;div&gt;{message}&lt;/div&gt; &lt;/div&gt;
template.breadcrumb_symbol :
template.parse_views false
assets.directories Array ( [base] =&gt; assets [cache] =&gt; cache [css] =&gt; css [image] =&gt; images [js] =&gt; js [module] =&gt; module )
assets.js_opener $(document).ready(function() {
assets.js_closer });
assets.css_combine false
assets.js_combine false
assets.css_minify true
assets.js_minify true
assets.encrypt_name false
assets.encode false
assets.base_folder assets
assets.asset_folders Array ( [css] =&gt; css [js] =&gt; js [image] =&gt; images )
ui.current_shortcuts Array ( [form_save] =&gt; Array ( [description] =&gt; Save any form in the admin area. [action] =&gt; $(&quot;input[name=save]&quot;).click();return false; ) [create_new] =&gt; Array ( [description] =&gt; Create a new record in the module. [action] =&gt; window.location.href=$(&quot;a#create_new&quot;).attr(&quot;href&quot;); ) [select_all] =&gt; Array ( [description] =&gt; Select all records in an index page. [action] =&gt; $(&quot;table input[type=checkbox]&quot;).click();return false; ) [delete] =&gt; Array ( [description] =&gt; Delete the record(s). [action] =&gt; $(&quot;#delete-me.btn-danger&quot;).click(); ) [module_index] =&gt; Array ( [description] =&gt; Return to the index of the current module. [action] =&gt; window.location.href=$(&quot;a#list&quot;).attr(&quot;href&quot;); ) [goto_content] =&gt; Array ( [description] =&gt; Jump to the Content context. [action] =&gt; window.location.href=$(&quot;#tb_content&quot;).attr(&quot;href&quot;) ) [goto_reports] =&gt; Array ( [description] =&gt; Jump to the Reports context. [action] =&gt; window.location.href=$(&quot;#tb_reports&quot;).attr(&quot;href&quot;) ) [goto_settings] =&gt; Array ( [description] =&gt; Jump to the Settings context. [action] =&gt; window.location.href=$(&quot;#tb_settings&quot;).attr(&quot;href&quot;) ) [goto_developer] =&gt; Array ( [description] =&gt; Jump to the Developer context. [action] =&gt; window.location.href=$(&quot;#tb_developer&quot;).attr(&quot;href&quot;) ) )
emailer.write_to_file false
migrate.auto_core false
migrate.auto_app false
commonmark.valid_drivers Array ( [0] =&gt; Parsedown [1] =&gt; Markdown [2] =&gt; MarkdownExtra [3] =&gt; LeagueCommonMark )
commonmark.driver MarkdownExtended
docs.theme docs
docs.default_group developer
docs.show_dev_docs true
docs.show_app_docs true
docs.toc_file _toc.ini
docs.permitted_environments Array ( [0] =&gt; development [1] =&gt; testing [2] =&gt; production )

Files

application.php
/var/www/clients/client2/web2/bonfire/application/config/application.php
autoload.php
/var/www/clients/client2/web2/bonfire/application/config/autoload.php
config.php
/var/www/clients/client2/web2/bonfire/application/config/config.php
constants.php
/var/www/clients/client2/web2/bonfire/application/config/constants.php
database.php
/var/www/clients/client2/web2/bonfire/application/config/database.php
events.php
/var/www/clients/client2/web2/bonfire/application/config/events.php
hooks.php
/var/www/clients/client2/web2/bonfire/application/config/hooks.php
mimes.php
/var/www/clients/client2/web2/bonfire/application/config/mimes.php
profiler.php
/var/www/clients/client2/web2/bonfire/application/config/profiler.php
routes.php
/var/www/clients/client2/web2/bonfire/application/config/routes.php
Base_Controller.php
/var/www/clients/client2/web2/bonfire/application/core/Base_Controller.php
MY_Model.php
/var/www/clients/client2/web2/bonfire/application/core/MY_Model.php
App_hooks.php
/var/www/clients/client2/web2/bonfire/application/hooks/App_hooks.php
application_lang.php
/var/www/clients/client2/web2/bonfire/application/language/english/application_lang.php
Profiler.php
/var/www/clients/client2/web2/bonfire/application/libraries/Profiler.php
Base.php
/var/www/clients/client2/web2/bonfire/application/third_party/MX/Base.php
Config.php
/var/www/clients/client2/web2/bonfire/application/third_party/MX/Config.php
Controller.php
/var/www/clients/client2/web2/bonfire/application/third_party/MX/Controller.php
Lang.php
/var/www/clients/client2/web2/bonfire/application/third_party/MX/Lang.php
Loader.php
/var/www/clients/client2/web2/bonfire/application/third_party/MX/Loader.php
Benchmark.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Benchmark.php
CodeIgniter.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/CodeIgniter.php
Common.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Common.php
Config.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Config.php
Controller.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Controller.php
Hooks.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Hooks.php
Input.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Input.php
Lang.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Lang.php
Loader.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Loader.php
Log.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Log.php
Model.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Model.php
Output.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Output.php
Router.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Router.php
Security.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Security.php
URI.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/URI.php
Utf8.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/Utf8.php
hash.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/compat/hash.php
mbstring.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/compat/mbstring.php
password.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/compat/password.php
standard.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/core/compat/standard.php
DB.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/DB.php
DB_driver.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/DB_driver.php
DB_query_builder.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/DB_query_builder.php
DB_result.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/DB_result.php
mysqli_driver.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/drivers/mysqli/mysqli_driver.php
mysqli_result.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/database/drivers/mysqli/mysqli_result.php
directory_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/helpers/directory_helper.php
form_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/helpers/form_helper.php
language_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/helpers/language_helper.php
url_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/helpers/url_helper.php
profiler_lang.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/language/english/profiler_lang.php
Cache.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Cache/Cache.php
Cache_dummy.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Cache/drivers/Cache_dummy.php
Driver.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Driver.php
Session.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Session/Session.php
Session_driver.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Session/Session_driver.php
Session_database_driver.php
/var/www/clients/client2/web2/bonfire/bonfire/ci3/libraries/Session/drivers/Session_database_driver.php
BF_Lang.php
/var/www/clients/client2/web2/bonfire/bonfire/core/BF_Lang.php
BF_Loader.php
/var/www/clients/client2/web2/bonfire/bonfire/core/BF_Loader.php
BF_Model.php
/var/www/clients/client2/web2/bonfire/bonfire/core/BF_Model.php
BF_Router.php
/var/www/clients/client2/web2/bonfire/bonfire/core/BF_Router.php
BF_Security.php
/var/www/clients/client2/web2/bonfire/bonfire/core/BF_Security.php
BF_directory_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/BF_directory_helper.php
BF_form_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/BF_form_helper.php
application_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/application_helper.php
config_file_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/config_file_helper.php
markdown_extended_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/markdown_extended_helper.php
markdown_helper.php
/var/www/clients/client2/web2/bonfire/bonfire/helpers/markdown_helper.php
Assets.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Assets.php
CommonMark.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/CommonMark.php
CommonMarkDriver.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/CommonMark/CommonMarkDriver.php
CommonMark_MarkdownExtended.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/CommonMark/drivers/CommonMark_MarkdownExtended.php
Console.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Console.php
Events.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Events.php
Modules.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Modules.php
Route.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Route.php
Template.php
/var/www/clients/client2/web2/bonfire/bonfire/libraries/Template.php
docs.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/config/docs.php
routes.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/config/routes.php
Docs.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/controllers/Docs.php
docs_lang.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/language/english/docs_lang.php
_sidebar.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/views/_sidebar.php
index.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/docs/views/index.php
Settings_lib.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/settings/libraries/Settings_lib.php
Settings_model.php
/var/www/clients/client2/web2/bonfire/bonfire/modules/settings/models/Settings_model.php
index.php
index.php
index.php
themes/docs/index.php