-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lighttpd.conf needs doesn't work #1876
Comments
You should rename all the references to
|
I did like I mentioned before. Grav is sitting in the www root. So I replaced all instances of /grav_path/ with null (thus removing it). I also tried replacing /grav_path/ with '/'. Didn't work either. |
Fixed by commenting out:
|
A little bit late, but after 3 years since this issue has been reported it seems that the lighttpd configuration still doesn't work out of the box. An alternative which seems to be working on my side, is the following: -url.access-deny = (".md","~",".inc")
+url.access-deny += (".md","~",".inc") Probably better than commenting the line, IMO. Based on the documentation, this should append the additional extensions to the option. It also works with |
@iulian3144 As you're on it, please look if you can match the rules from None of the developers have the Lighttpd server installed making me scared to update the file blindly. |
@mahagr I actually started messing with lighttpd the day before I added my comment. |
I moved the lighttpd.conf to /etc/lighttpd/conf-available/. Right now the server can only load the default page, but no other pages (404).
Now I do:
lighty-enable-mod lighttpd
which enables the config. But after this lighttpd won't start anymore. The logs mention multiple files (the server config, the grav config and the perl file that includes configs).
When I disable the config, the default page works again, but nothing else.
The only thing I changed in the config was (using vim):
:%s/\/grav_path\///g
and I manually edited the one on line 45 (removed "/grav_path").
The text was updated successfully, but these errors were encountered: