GetPageSpeed keeps NGINX and Varnish servers fast and secure: performance modules and builds, plus security fixes within days, all through routine
Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days.
dnf, yum or apt upgrades. It maintains the largest RPM repository of NGINX module packages and Varnish VMODs, with APT packages for Debian and Ubuntu.
Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days.
Ever seen a message in your iTerm or Terminal apps telling you there’s a problem setting locale?
It may be when you run a Perl app:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = “UTF-8”,
LANG = “en_US.UTF-8”
are supported and installed on your system.Or even more likely, once you initiated a connection to remote server via SSH:
-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directoryThere are many ways you can find online suggested as the fix. But what is the scientifically correct answer to the problem?
Many suggest that your server is flawed and is missing a locale. They suggest to generate one. But it’s not technically a valid locale “UTF-8”.
Your server is not flawed. OS X default SSH client configuration is.
Add to your ~/.profile:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8