need a bit of help

[eluser]thatphpguy[/eluser]
Sorry if this seems like a real "noob" question but, I installed the CI system onto my web server, but I would like to know how to make it so the url can look like this:

http://www.domain.com/project/

instead of...

http://www.domain.com/index.php/project/

is this possible?

[eluser]Randy Casburn[/eluser]
It is extremely obscure in the documentation (well, not really)

It is under the heading:

Removing the index.php file

in the section called CodeIngiter URIs

Go Figure...the documentation really is amazing.

Randy

[eluser]thatphpguy[/eluser]
This helps for the most part,

but I know nothing about .htaccess files, could anyone maybe help me out further?
I copied the example given in the docs, but do not know what to add to have it so all my controllers/models/views aren't redirected to index.php

[eluser]Randy Casburn[/eluser]
And all of ten seconds...

http://httpd.apache.org/docs/2.0/howto/htaccess.html

help thy self...you will find great help here as well

[eluser]thatphpguy[/eluser]
Thanks for the help

[eluser]Randy Casburn[/eluser]
OK...now that we're past the "please search the forums and read the documentation - then ask your questions because you'll be able to frame them a lot better" ...

what the .htaccess file does is allow your URIs to exclude the 'index.php' part of the URL, but it (the .htaccess file) is going to magically stuff it back into the URI. Now the reason 'index.php' has to get stuffed back in is because 'index.php' must be in the URI for CodeIngiter to work properly since the entire system is kicked off by a scripted named 'index.php'.

So the bottom line here is that your end users won't see 'index.php' in the browser address bar, but .htaccess is required in order to stuff 'index.php' back into the URI so it will be properly formed. That means including 'index.php'.

Now, the trick is getting it to work on your specific server platform. There are many variations on that particular theme. So please search this form for topics covering .htaccess setups for your server operating system and configuration. That will be the speediest way to get those problems resolved.

I hope this is more useful.

Randy

[eluser]thatphpguy[/eluser]
I've already solved my problem, but uhh, thanks again, this time for explaining

[eluser]Randy Casburn[/eluser]
You're welcome