- For alternative server configurations (such as Nginx server and MariaDB
- database engine, refer to the wiki at https://github.com/friendica/friendica/wiki
+ database engine), refer to the wiki at https://github.com/friendica/friendica/wiki
2. Unpack the Friendica files into the root of your web server document area.
3. Create an empty database and note the access details (hostname, username,
password, database name).
+ - Friendica needs the permission to create and delete fields and tables in its own database.
+
4. If you know in advance that it will be impossible for the web server to
write or create files in your web directory, create an empty file called
and save your changes.
+9. (Optional) Reverse-proxying and HTTPS
+
+Friendica looks for some well-known HTTP headers indicating a reverse-proxy
+terminating an HTTPS connection. While the standard from RFC 7239 specifies
+the use of the `Forwaded` header.
+
+ Forwarded: for=192.0.2.1; proto=https; by=192.0.2.2
+
+Friendica also supports a number on non-standard headers in common use.
+
+
+ X-Forwarded-Proto: https
+
+ Front-End-Https: on
+
+ X-Forwarded-Ssl: on
+
+It is however preferable to use the standard approach if configuring a new server.
-
#####################################################################
If things don't work...