/ fuel/ app/ core/ packages/ public_html/ public/ .htaccess assets/ index.php oil
/ |- app-1 |- app-2 |- FUEL-for-app-1 |- FUEL-for-app-2
Guido R wrote on Saturday 7th of May 2011:Thanks, I've got it now! But isn't this something that can be mitigated with an .htaccess file and "Deny from all" and then on every php file, the first line something like:<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');as CI does? which is a better practice? because I think some hostings doesn't execute the php files outside the document root
/ --fuel/ ----app/ ----core/ ----packages/ --public_html/ ----.htaccess ----assets/ ----index.php ----oilEdit: fixing formatting. Maybe this forum should be open-sourced so that someone who's got time can work on the many deficiencies.
Jelmer Schreuder wrote on Friday 6th of May 2011:
/ (??) is this public_html? fuel/ app/ core/ packages/ public/ .htaccess assets/ index.php oil
Move the files to your server:
- Note the public directory in the source equals your web server's public document directory i.e. public_html, public, htdocs, etc. Move its contents to there or a subdirectory of the webroot where you want to use Fuel.
- Placing the fuel directory outside of the public document directory is encouraged for security reasons.
- Edit the paths in index.php to point to your app, core & packages directories.
<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed');as CI does? which is a better practice? because I think some hostings doesn't execute the php files outside the document root
It looks like you're new here. If you want to get involved, click one of these buttons!