Slight config change for those using nginx and getting erratic /index.php/ file paths #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For some strange reason, Gallery3 under nginx prefers not to have this setting (note: I've kept it as a commented option)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gallery3 users are mostly Apache-bound, but the underlying framework, Kohana 2, even though it's ancient, supports nginx as well. A working nginx configuration for Galery3 has already been developed by @jonmiller and is described on #8.
I'm not quite sure where such a configuration file ought to be placed, so that nginx users are able to find it; perhaps some day the Gallery3 wiki is available in some form again, and becomes editable once more, thus allowing the corrected nginx configuration to be placed there...
There is, however, a catch, which Jon Miller has found and fixed: the configuration file on
./application/config/config.phpneeds to have:I keep forgetting to change that :-) so I'm submitting a PR where this option is in the configuration file, but commented out by default, with a small note to potential nginx users to remove it. As said, in the future, hopefully we can place such notes and comments to an official online 'manual' for Gallery3.
The changes made to
.gitignoreare essentially to clean up the garbage generated by developing under macOS :-PSee also the discussion around the nginx configuration (and lots of personal rants...) on https://groups.google.com/g/gallery-3-users/c/7DXCw2slny8/m/UruqyKymAgAJ
Caveat utilitor: this PR does not fix everything for nginx installations! Like Apache installations, nginx varies a lot from system to system, and may or may not be fully configurable on hosted environments. I use Gallery3 on my own self-compiled nginx on a 'bare metal' server, which means I've got full access to every little aspect on my system, and I'm therefore able to get Gallery3 running flawlessly on my environment. YMMV.
Potentially closes #8.