-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Work in Progress] creating cookbook / webservers_configuration page #1705
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
Conversation
Please correct your article confirm the Doc Standards, you should end your line after the first word that crosses the 72 character and you should indent everything in a block ( |
RewriteEngine On | ||
RewriteCond %{REQUEST_FILENAME} !-f | ||
RewriteRule ^(.*)$ /app.php [QSA,L] | ||
</IfModule> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Imo, we should show AllowOverride All
and not include the mod rewrite options here. Then, we can add a note saying that for performance, you may choose this other option.
My goal is to keep this as simple as possible, so people understand the minimum required. Imo, I think we should also remove the Options ...
, Order allow,deny
and allow from all
lines - they're not strictly needed to get things up and running. Same thing with ServerAlias
and ServerAdmin
.
But, if anyone disagrees on any points, please let me know!
Hi there! I really like the idea of this article - we just need much much less for our original version :). I'd like to show only the bare minimum of what's necessary. Of course, I'm definitely open to additional notes on some very fundamental things that might also be helpful, but I don't want those extras to "cloud" how simple things should be. So, if we can get each part down to the simplest examples, we should have a good start. Then we can start adding more notes for extra things. We also need to get more "eyes" on this - I'm certainly not an expert in nginx and lighttpd - but many other people are :). Thanks! |
Ping @tkoomzaaskz and anyone else! I do like the idea behind this PR, but it still needs some work. I left several comments - if we can follow those (and add any other comments that are needed), then I think we can get much closer. Thanks! |
We should also tweak this document conform the standards, the indention isn't right and lines don't stop around the 72th character, ect. |
what is the status of this document, @tkoomzaaskz & others? |
The nginx configuration is quite verbose. The example provided on the nginx wiki is the most suitable configuration (and the most safe). The single thing to note with the proposed configuration (as per the wiki) is that it limits php execution inside /web to just app.php and app_dev.php. |
Yes, I think for Nginx we should just link to that Wiki, them maybe add some additional notes as @merk is suggesting. |
I'm closing this PR in favor of #2410. @tkoomzaaskz thanks for getting this started! |
I have created an initial page content, based on issue #578. I know it's not perfect (hopefully, not far from perfect), but now it should be easier to continue and deliver a nice article. Anyone having knowledge about nginx and lighttpd is welcome :)