| # put this file in /etc/systemd/system/ as root | |
| # below paths assume solr installed in /opt/solr, SOLR_PID_DIR is /data | |
| # and that all configuration exists in /etc/default/solr.in.sh which is the case if previously installed as an init.d service | |
| # change port in pid file if differs | |
| # note that it is configured to auto restart solr if it fails (Restart=on-faliure) and that's the motivation indeed :) | |
| # to switch from systemv (init.d) to systemd, do the following after creating this file: | |
| # sudo systemctl daemon-reload | |
| # sudo service solr stop # if already running | |
| # sudo systemctl enable solr | |
| # systemctl start solr |
| user nginx; | |
| # one(1) worker or equal the number of _real_ cpu cores. 4=4 core cpu | |
| worker_processes 4; | |
| # renice workers to reduce priority compared to system processes for | |
| # machine health. worst case nginx will get ~25% system resources at nice=15 | |
| worker_priority -5; |
| # | |
| # Auth filter /etc/fail2ban/filter.d/nginx-auth.conf: | |
| # | |
| # Blocks IPs that makes too much accesses to the server | |
| # | |
| [Definition] | |
| failregex = ^<HOST> -.*"(GET|POST).*HTTP.*" | |
| ignoreregex = |
This Gist is a collection of configuration files that can be used to easily setup a Homebrew-based LEMP stack on Mac OS X.
Files in this repository are numbered and named for ordering purposes only. At the top of each file is a section of metadata that denote what component the file belongs to and the default name & location of the file. Feel free to implement it however you want.
Note: some configuration files have hard-coded paths to my user directory -- fix it for your setup
This tutorial walks through setting up AWS infrastructure for WordPress, starting at creating an AWS account. We'll manually provision a single EC2 instance (i.e an AWS virtual machine) to run WordPress using Nginx, PHP-FPM, and MySQL.
This tutorial assumes you're relatively comfortable on the command line and editing system configuration files. It is intended for folks who want a high-level of control and understanding of their infrastructure. It will take about half an hour if you don't Google away at some point.
If you experience any difficulties or have any feedback, leave a comment. 🐬
Coming soon: I'll write another tutorial on a high availability setup for WordPress on AWS, including load-balancing multiple application servers in an auto-scaling group and utilizing RDS.
| #!/usr/bin/env bash | |
| if [ "$EUID" -ne 0 ];then | |
| >&2 echo "This script requires root level access to run" | |
| exit 1 | |
| fi | |
| if [ -z "${WORDPRESS_DB_PASSWORD}" ]; then | |
| >&2 echo "WORDPRESS_DB_PASSWORD must be set" | |
| >&2 echo "Here is a random one that you can paste:" |