Love Fuel?    Donate

FuelPHP Forums

Ask your question about FuelPHP in the appropriate forum, or help others by answering their questions.
Setup in sub directory on shared host
  • Hey Guys, Going well so far with fuelPHP, loving it! I need some help with setting up my fuelPHP project that I have developed locally.
    I now need to move it to my hosted server, which is a shared host environment. Now I'm hoping to setup my project under a sub directory on the shared host, at the moment there are some other files in the documentRoot which can't really be moved right now. So is it possible to setup my fuelPHP to run in a sub directory, like ? Directory structure layout for clarification; DocumentRoot (
    -> subdir
    --> -> fuel
    --> -> public
    -->-> oil
  • What is going to be in that subdir? From your directory structure I see you have everything in the docroot?
  • Hmm, I see that it didn't keep my formating, although I should have checked my post properly after posting. Anyway fuel,public,oil should be inside the sub-directory
  • Ok, I thought so. That is not a problem, but requires a custom .htaccess in your subdir, with the correct rewrite rules so that loads the index.php that is in /subdir/public. You find some information here: Adapt it to take the extra subdir into account.
  • Alrighty, well I had a look at these, and for testing purposes it doesn't have to have really clean url's.
    So on my localhost I can access my fuelPHP app via - [url=http://localhost/ijob_admin/public/]http://localhost/ijob_admin/public/[/url] which takes me the route for the home page of the app. all works fine.
    Although trying to access it from my hosted server using the same method and .htaccess files,
    Gives me " Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error" Maybe there is some other sort of setup I need to do in the config files ? Everything is the same though..
  • Chrome? From what I understand, it's either a Chrome bug (which can be fixed by restarting), or a setting on the server that is wrong, and causes a GZIP encoding mismatch (either the content is encoded, but it's not mentioned in the HTTP header, or it is not encoded, but mentioned in the header).
  • Correct, Chrome. I also tried in Firefox now, and it came back with a " invalid or unsupported form of compression "
    So that must be a server setting on the compression, damn, thats going to be awesome to try and sort out....
  • If you haven't configured an ob_callback in your application configuration, your FuelPHP app doesn't do compression. So it must be that either the servers php.ini file enables compression by default, or there's a webserver module that does that.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion