Announcing Bonfire - A jumpstart for your web apps

[eluser]Basketcasesoftware[/eluser]
Good news. The latest Bonfire build installed and ran successfully on the host. The account reset seems to have done the ticket. My host just put in new machines and it looks like there might have been bugs yet. They take the trouble to keep their system up to date with the latest LAMP architecture so I have to give them some wiggle room there. I know that can't be at all easy for such a large client base as they have.

[eluser]kilishan[/eluser]
@Basketcasesoftware - Awesome news!

[eluser]Basketcasesoftware[/eluser]
[quote author="kilishan" date="1303725150"]@Basketcasesoftware - Awesome news![/quote]
Had the same problem initially on my local host just now. My databases both at home and on my host are created with phpMyAdmin - common enough. When I created the basic db on my home machine and did a simple import of the db and files from my host there was a connection failure. I changed my privileges from '%' to 'localhost' and then recreated the db with the collation and MySQL connection collation as utf8_general_ci. re-imported the data - BINGO!
Very strange indeed.

Quick question. How you change the DB's mode? I'm stuck in development and I don't find anything in the CP to change it. Also where do the Auth functions live. They aren't under libraries that I can see.

[eluser]kilishan[/eluser]
Yeah, that is pretty strange. I know that I typically set collation to utf8_general_ci when I create a new db. Wonder if that's been causing the issue all along. Definitely something to look into.

Thanks

[eluser]Basketcasesoftware[/eluser]
In the Assets class you create functions for locating css and js files, but nothing for other media, even though you have an 'image' category in one of your arrays.
I added a quick function to the Assets class but it's a hack. It would be better if it was using the find_files function. Here's the code that I placed immediately after the Assets::image() function.

Code:

public static function image_path($image=null)
{
  if (empty($image)) return '';
  
  return(self::$asset_url . self::$asset_base . self::$asset_folders['images'] .'/'. $image);
}

Edit: Oops. Wrong version. Here's the working one.

Code:

public static function image_path($image=null)
{
  if (empty($image)) return '';
  
  $site_path = base_url() . self::$asset_base .'/';
  
  return($site_path . self::$asset_folders['image'].'/'. $image);
}

[eluser]kilishan[/eluser]
[quote author="Basketcasesoftware" date="1303773529"]Quick question. How you change the DB's mode? I'm stuck in development and I don't find anything in the CP to change it. Also where do the Auth functions live. They aren't under libraries that I can see.[/quote]

You're right. There's nothing in the CP to change that. You'll have to edit the application/config/database.php and application/config/development/database.php config files manually.

The Auth functions are in the users core_module, so you'll find them under application/core_modules/users/libraries/auth.php

[eluser]kilishan[/eluser]
[quote author="Basketcasesoftware" date="1303774387"]In the Assets class you create functions for locating css and js files, but nothing for other media, even though you have an 'image' category in one of your arrays.
I added a quick function to the Assets class but it's a hack. It would be better if it was using the find_files function. Here's the code that I placed immediately after the Assets::image() function.

Code:

public static function image_path($image=null)
{
  if (empty($image)) return '';
  
  return(self::$asset_url . self::$asset_base . self::$asset_folders['images'] .'/'. $image);
}

[/quote]

Yeah, the images portion of the assets is under-developed at the time. In time, I'd like to make it handle image resizing based on location, as well as make it simple when you have to change your media from a local server (like under media.myserver.com) to residing on a CDN like Amazon S3. Obviously, not there yet.

You could use the find_files function if you want the image to be able to be overridden by child themes, or potentially exist in the default theme, but not in the child theme and still be found. If you don't need that ability, then there's no need for the find_files method to be called. It's faster without using that function anyway, but once things get cached, it doens't make a difference anymore.

So, it all depends on the type of site you're creating, I guess.

[eluser]Basketcasesoftware[/eluser]
How do I get that profiler bar to go away? It won't do on a production site and I don't see anything in the control panel, any of the config files, or anywhere else. It just happily inserts itself at the bottom of any page (including the admin section), and if I delete the profiler_template file I just get an error message. I can't find anything in the docs about it at all - it's just there. Even your thumbnails in this thread have it. It's nice to have (if it worked for me consistently) in development, but I'm near release and it's GOT to go.

[eluser]kilishan[/eluser]
The profiler will only show up on development environments.

This is controlled in the Base_Controller's constructor. The code is:

Code:

if (ENVIRONMENT == 'development')
        {
            $this->load->library('Console');
            
            if (!$this->input->is_cli_request())
            {
                $this->output->enable_profiler(true);
            }
        }

Feel free to modify as needed.

[eluser]kilishan[/eluser]
@Basketcasesoftware - when you get it launched and live, I'd love it if you could take a few minutes and tell me about your experience developing with Bonfire. What things were made better? What things did you find difficult? What could make the development process easier? Any other tools you'd like to see? Stuff like that.