clones/friendica
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Modify nginx sample to a real config file

This commit is contained in:
Olaf Conradi 2012-12-15 16:01:20 +01:00
parent 6b36863dd8
commit b38b62f759
1 changed files with 34 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

63
mods/sample-nginx.config
View File

@ -1,19 +1,31 @@
From: Olaf Conradi ##
Hey @Friendica Support, # Friendica Nginx configuration
# by Olaf Conradi
#
# On debian based distributions you can add this file to
# /etc/nginx/sites-available
#
# Then customize to your needs. To enable the configuration
# symlink it to /etc/nginx/sites-enabled and reload Nginx
# using /etc/init.d/nginx reload
##
Just wanted to share my #nginx configuration for #friendica with you guys. ##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
#
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
##
I noticed most of the existing configurations that are floating on the web for #nginx do not deny access to local files. Most of them use the following construct. ##
# This configuration assumes your domain is example.net
location / { # You have a seperate subdomain friendica.example.net
try_files $uri $uri/ index.php?q=$request_uri # You want all friendica traffic to be https
} # You have an SSL certificate and key for your subdomain
# You have PHP FastCGI Process Manager (php5-fpm) running on localhost
This serves files like images statically, but also gives everyone access to the source code of your ~friendica ~friendica installation (tpl templates, sql files, etc). One should deny all locations except for images, javascript and css files. Setting these deny rules is tedious and needs maintenance when new directories are added. ##
It's easier to route everything through the front controller except those known file types.
Below is my configuration. First I forward non-SSL traffic to SSL.
server { server {
server_name friendica.example.net; server_name friendica.example.net;
@ -22,7 +34,14 @@ server {
rewrite ^ https://friendica.example.net$request_uri? permanent; rewrite ^ https://friendica.example.net$request_uri? permanent;
} }
Next is the SSL server part. ##
# Configure Friendica with SSL
#
# All requests are routed to the front controller
# except for certain known file types like images, css, etc.
# Those are served statically whenever possible with a
# fall back to the front controller (needed for avatars, for example)
##
server { server {
listen 443 ssl; listen 443 ssl;
@ -88,17 +107,3 @@ server {
} }
} }
That's it.
#nginx #friendica @Friendica Support
I found one bug after posting when I noticed 404's coming in for certain image files. Avatars need a fallback to go through the front controller.
# statically serve these file types when possible
# otherwise fall back to front controller
# allow browser to cache them
# added .htm for advanced source code editor library
location ~* \.(jpg|jpeg|gif|png|css|js|ico|htm)$ {
expires 30d;
try_files $uri /index.php?q=$request_uri?;
}