Interesting Take On A Wiki - Testing Now
-
Dont specify a zone and it will default to the current one in use...
-
@black3dynamite said in Interesting Take On A Wiki - Testing Now:
I've got it. In
/etc/httpd/conf/httpd.conffile.Changing
<Directory "/var/www/html">to<Directory "/var/www/html/bookstack/public">
And also changingAllowOverride NonetoAllowOverride Allfixes the not found page.Just tested this and it does resolve the issues.
But, I think it will be cleaner to use the vhost file simply named bookstack.conf -
@tim_g said in Interesting Take On A Wiki - Testing Now:
Dont specify a zone and it will default to the current one in use...
-
I will clean up the above instructions and make a how to install post today.
-
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@dafyre said in Interesting Take On A Wiki - Testing Now:
So from start to finish, running JB's script everything worked for me out of the box, except for one thing. I had to
firewall-cmd --set-default-zone=publicBut that may be because my install was done with the Server DVD and not a minimal install.
Not my problem that you failed to follow instruction.
Yes, yes, I know. I posted that for others who don't follow your instructions.
Admittedly, I did look for the "Minimal" option, but that must not be available on the 2GB iso.
-
The WSYWIG editor is pretty cool... You can paste in images and such from the clipboard.
It also integrates with Draw.io for inserting diagrams into your page.
-
Dev closed the issue stating they don't want the conf file in the repo for silly reasons.. but meh.. instructions coming shortly.
following my own instructions one more time with the target of making a guide.
-
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL? -
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?You don't need to do anything with SSL to make it work. Works by default.
-
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
-
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
Interesting.
After I installed it and got all the Composer packages updated and migrated the DB and all those things, ready to open it, it refused to open, it immediately redirects to https. I looked in htaccess files for any kind of redirect but didn't see it.
What else could be making it switch to https on its own?
-
@guyinpv said in Interesting Take On A Wiki - Testing Now:
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
Interesting.
After I installed it and got all the Composer packages updated and migrated the DB and all those things, ready to open it, it refused to open, it immediately redirects to https. I looked in htaccess files for any kind of redirect but didn't see it.
What else could be making it switch to https on its own?
Are you using my actual guide or the temp notes that were posted earlier in this thread?
Actual Guide: https://mangolassi.it/topic/16471/install-bookstack-on-fedora-27
-
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
Interesting.
After I installed it and got all the Composer packages updated and migrated the DB and all those things, ready to open it, it refused to open, it immediately redirects to https. I looked in htaccess files for any kind of redirect but didn't see it.
What else could be making it switch to https on its own?
Are you using my actual guide or the temp notes that were posted earlier in this thread?
Actual Guide: https://mangolassi.it/topic/16471/install-bookstack-on-fedora-27
The
.envfile contains an APP_URL value that it will force redirect to if uncommented. -
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
Interesting.
After I installed it and got all the Composer packages updated and migrated the DB and all those things, ready to open it, it refused to open, it immediately redirects to https. I looked in htaccess files for any kind of redirect but didn't see it.
What else could be making it switch to https on its own?
Are you using my actual guide or the temp notes that were posted earlier in this thread?
Actual Guide: https://mangolassi.it/topic/16471/install-bookstack-on-fedora-27
I just followed regular old install instructions https://www.bookstackapp.com/docs/admin/installation/
Everything worked fine up until opening it. But of course that could be due to who knows what goofy WAMP config with virtual host and all that.
I'm now giving it another go on a dedicated cPanel on a VPS to see if that works better.
-
@guyinpv said in Interesting Take On A Wiki - Testing Now:
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
It forces https? I just wanted to throw it up into WAMP but don't want to fart with trying to make SSL work on it.
Any way to disable that and play with it without SSL?It absolutely does not use SSL by default.
No idea what you did to think that.
Now, I would never use it without SSL. But that is different.
Interesting.
After I installed it and got all the Composer packages updated and migrated the DB and all those things, ready to open it, it refused to open, it immediately redirects to https. I looked in htaccess files for any kind of redirect but didn't see it.
What else could be making it switch to https on its own?
Are you using my actual guide or the temp notes that were posted earlier in this thread?
Actual Guide: https://mangolassi.it/topic/16471/install-bookstack-on-fedora-27
I just followed regular old install instructions https://www.bookstackapp.com/docs/admin/installation/
Everything worked fine up until opening it. But of course that could be due to who knows what goofy WAMP config with virtual host and all that.
I'm now giving it another go on a dedicated cPanel on a VPS to see if that works better.
There is no guide there I don't know WTF you are talking about.
They have "9 steps", an Ubuntu script, a community docker install and some "security engineer" with a CentOS 7 install and telling you to disable SELinux and the firewall.
-
That's right. 9 steps to install it via Composer. All that worked except for forcing https which didn't work on my WAMP.
I'm doing it again on cPanel but have to finish tomorrow.
-
@guyinpv said in Interesting Take On A Wiki - Testing Now:
That's right. 9 steps to install it via Composer. All that worked except for forcing https which didn't work on my WAMP.
I'm doing it again on cPanel but have to finish tomorrow.
Except it isn't. Those 9 steps are assuming all kinds of things.
-
@guyinpv said in Interesting Take On A Wiki - Testing Now:
That's right. 9 steps to install it via Composer. All that worked except for forcing https which didn't work on my WAMP.
I'm doing it again on cPanel but have to finish tomorrow.
why don't you do it on Linux following JB's guide?
-
@tim_g said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
That's right. 9 steps to install it via Composer. All that worked except for forcing https which didn't work on my WAMP.
I'm doing it again on cPanel but have to finish tomorrow.
why don't you do it on Linux following JB's guide?
Because this guy is worse than @Dashrender about doing things the hard way.
-
@jaredbusch said in Interesting Take On A Wiki - Testing Now:
@tim_g said in Interesting Take On A Wiki - Testing Now:
@guyinpv said in Interesting Take On A Wiki - Testing Now:
That's right. 9 steps to install it via Composer. All that worked except for forcing https which didn't work on my WAMP.
I'm doing it again on cPanel but have to finish tomorrow.
why don't you do it on Linux following JB's guide?
Because this guy is worse than @Dashrender about doing things the hard way.
That's funny. Their tutorial was far less hard than yours, and yours didn't cover my environment. But thanks anyway.
I was on a WHM/cPanel setup on a VPS. While I did have SSH access as root, I used my cpanel user only at first. Apache and MySQL, not Nginx and MariaDB. But anyhoo.
Problem 1: Changing documentroot for Apache. I had the host do this, even though I could do it from root. Otherwise use of /public folder wouldn't work. Anybody on a cPanel would have to do this. If the site is an "addon" domain, it's easy, but if it's the primary domain (as mine was), the process is a little more involved.
Problem 2: I got a "No input file specified" blank page when trying to open it. This apparently had something to do with using fastCGI or PHP-FPM or something. Again the host made a server change, I believe all they did was turn off PHP-FPM. (this site is using PHP 7.2).
Problem 3: After fixing that, the site was redirecting to the /login address but simply went to 404. To fix this, I had to do a bunch of Composer things, update Composer itself, global self-update, enable fopen urls until finally Composer had no warnings or errors when updating. When I first ran composer update, it downloaded everything and created the vendor folder, but apparently it still couldn't work because of version issues between Laravel and artisan and composer or some weird nonsense. I needed su ability to get composer updated here.
Problem 4: Nothing worked yet, because when the host messed with PHP it generated a new htaccess file and left out all the stuff in the default one. I fixed that up.
Problem 5: Site now loads without 404 error, but instead just throws a server 500. The Illuminate package had permission errors writing in the Storage folder even with 755 permissions. To fix this (as other suggested online), I set folders to 777.
Then I had to runartisan cache:clearandcomposer dump-autoload. In general I always thought 777 was anathema but that's what everybody said to do.I finally got the freaking login after that.
Problem 6: It still couldn't upload files to the uploads folder, so again had to go set 777. For the heck of it, I went and set bootstrap/cache to 777 too since that is the third folder they wanted to ensure write access. Now pictures could upload.
Now finally the installation is working.
Just by way of reference for anybody else who uses a cPanel setup. Composer was just there already on the VPS, but not up to date. And when using su, the Composer path is not set in globals so I had to reference full path.
Documentroot needs changed (including addition config if using SSL).
Potentially FastCGI issues. Some of this can be changed from WHM.
Give full 777 folder permissions.Profit.
