Scratch

jvvg wrote:

So from what it seems, the installation process is much trickier than it looked at first. If your server has the right settings by default, it is fairly easy to install. However, if anything is different, such as not being able to overwrite the .htaccess file, not having AllowOverride on, not having the right Apache modules installed, etc. then it won't work. I will write a guide explaining all of the settings that need to be in place to allow FutureBB to install.

Or the .htaccess file not existing at all.    Had to create a blank one to make the installer happy. Forum still doesn't work though. 

jvvg wrote:

fire219 wrote:

jvvg wrote:

So from what it seems, the installation process is much trickier than it looked at first. If your server has the right settings by default, it is fairly easy to install. However, if anything is different, such as not being able to overwrite the .htaccess file, not having AllowOverride on, not having the right Apache modules installed, etc. then it won't work. I will write a guide explaining all of the settings that need to be in place to allow FutureBB to install.

Or the .htaccess file not existing at all.    Had to create a blank one to make the installer happy. Forum still doesn't work though. 

What happens now?

Well... I used the root web directory (var/www) as the forum root (because I was getting HTTP 403s when it was in its own subdirectory), and after the setup, I still got my original homepage... I'm trying clearing it all and starting over fresh (without anything but futurebb).

Last edited by fire219 (2013-04-12 21:31:58)

jvvg wrote:

fire219 wrote:

jvvg wrote:

What happens now?

Well... I used the root web directory (var/www) as the forum root (because I was getting HTTP 403s when it was in its own subdirectory), and after the setup, I still got my original homepage... I'm trying clearing it all and starting over fresh (without anything but futurebb).

I had this issue on Linux, and you either need to set AllowOverride to All or somehow otherwise get Apache to rewrite all requests to dispatcher.php.
In the full release, I will make a much simpler option where the URLs just go to /dispatcher.php/someurl if the user doesn't want to configure the rewrites.

I'm using nginx... no AllowOverride (or .htaccess files, for that matter)

Seems that me stubbornly sticking with nginx is causing 95% of the problems. 

jvvg wrote:

fire219 wrote:

jvvg wrote:

I had this issue on Linux, and you either need to set AllowOverride to All or somehow otherwise get Apache to rewrite all requests to dispatcher.php.
In the full release, I will make a much simpler option where the URLs just go to /dispatcher.php/someurl if the user doesn't want to configure the rewrites.

I'm using nginx... no AllowOverride (or .htaccess files, for that matter)

Seems that me stubbornly sticking with nginx is causing 95% of the problems. 

That's an issue. I only designed this to work with Apache.

But apache is slow and inefficient. :c



I guess I'll switch it to apache when I get on my computer (on phone atm).

jvvg wrote:

fire219 wrote:

jvvg wrote:

That's an issue. I only designed this to work with Apache.

But apache is slow and inefficient. :c



I guess I'll switch it to apache when I get on my computer (on phone atm).

I read somewhere that Apache is the best server software for dynamic websites, while pretty lousy for static websites.

Maybe..it's easier to configure than nginx, at least... Getting PHP working on nginx took about an hour.

Anyway, running with Apache: After deleting and reinstalling the database, the installation ran smoothly (until having to make another .htaccess file). Once the installation was done, going to the main page of the site just resulted in a directory list.