-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
AppStarter Vanilla Installation - No hint that writable directory is not writable #1934
Comments
Just noticed that this is perfectly documented when one changes the environment to "development". I'll close the issue although I am not super happy with this behaviour. Might or might not discourage newbies to PHP/CodeIgniter; even an experienced dev like me did not think automatically that the default environment may prevent helpful error messages from displaying. Maybe a little hint on the installation page may not be the worst idea, but thats up to the devs. |
Which OS are you using? When I install the appstarter on Linux, it results in app, public & vendor all writable |
Writable yes, but for the wrong user.
|
I see it user (you) and group writable. Who should it be writable for? |
The apache user! On Ubuntu&Co |
Hmmm - I think that will have to go in the writeup rather than the script, then, as that could vary between platforms. |
Just installed CI4 via AppStarter, changed nothing more than the
baseURL
and got a500
in the browser saying"Whoops! We seem to have hit a snag. Please try again later..."
.Digging deeper I found out that there happens a call to a
cache()->get()
-function which checks if the current request is already cached. Combined with the finding, that the default cache handler is "file", I guessed and made thewritable
directory writable forwww-data
and the request succeeded.Neither the installation section in the CI4-docs nor the CI4-error message gave me a hint to the correct direction. Maybe one of those two could be optimized (preferring a more meaningful 500 error message). It was just experienced PHP-dev intuition and debugging in the
vendors
directory, which not everyone may be capable of, that lead me to the right fix.The text was updated successfully, but these errors were encountered: