| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Without gzip explicitly enabled, load times suffer from transferring
over a megabyte of plaintext javascript. With gzip enabled, the bundle
is down to about 300K, and loads much faster.
This change does not enable gzip on files that are already compressed,
so images, fonts, and videos will be sent without the CPU overhead.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
(#364)" (#365)
This reverts commit d40cd86bf56973d7217ad44737e3890b6e7f1ad5.
|
| | |
|
| |
|
| |
`X-Frame-Options DENY;` doesn't permit sharing using iframe
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- added precisions and suggestions about how to generate Let's Encrypt certificates. Users have reported their installations didn't work when the problem came from missing certificates (false positives).
- security defaults of Nginx follow the basic robustness principle "be conservative in what you send, be liberal in what you accept", which isn't enough with modern security standards, so we should be picky with the cipher suites we use, among other things. Extra comments (especially for the TLS1.3 protocol support parameter) make the requirement of a recent Nginx installation obvious, and the downgrade alternative remains clear to the system administrator.
All in all, we should aknowledge users will most often copy and paste the configuration files. Making them secure by default may force a few users to read their configuration, but on the long run we are making the fediverse more secure.
Since I've come to modify a bit the Nginx config in `support/doc/production.md`, I've merged it with the template so that they stay consistent.
|
| | |
|
| |
|
|
| |
We need to maintain a cache in the node process
|
| | |
|
| |
|
|
|
| |
Use release that already contains build files. It requires a specific
directories tree but I think it would be fine.
|
| |
|
|
| |
And update nginx configuration with a rate limit
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
