This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.
Workshop Instructor:
- Lilly Ryan @attacus_au
This workshop is distributed under a CC BY-SA 4.0 license.
############################################################################### | |
# Install MySQL Server 5.7 on Ubuntu 16.04 LTS | |
############################################################################### | |
# Download and Install the Latest Updates for the OS | |
apt update && apt upgrade -y | |
# Install MySQL Server in a Non-Interactive mode. Default root password will be "root" | |
echo "mysql-server-5.7 mysql-server/root_password password root" | sudo debconf-set-selections | |
echo "mysql-server-5.7 mysql-server/root_password_again password root" | sudo debconf-set-selections |
<?php | |
/** | |
* Created by jamiesonroberts | |
* Date: 2017-04-08 | |
*/ | |
/** | |
* Removes security vulnerabilities, extraneous styles and scripts, | |
* as well as related resource inclusions for Wordpress 4.7.x | |
* |
This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.
Workshop Instructor:
This workshop is distributed under a CC BY-SA 4.0 license.
<?php | |
/** | |
* Programmatically install and activate wordpress plugins | |
* | |
* Usage: | |
* 1. Edit the $pluginSlugs array at the beginning of this file to include the slugs of all the | |
* plugins you want to install and activate | |
* 2. Upload this file to the wordpress root directory (the same directory that contains the | |
* 'wp-admin' directory). | |
* 3. Navigate to <your-domain-wordpress-root>/install-wp-plugins.php (If wordpress is installed |
sudo apt-get install build-essential tcl
cd /tmp
curl -O http://download.redis.io/redis-stable.tar.gz
tar xzvf redis-stable.tar.gz
############## | |
# pretty prompt and font colors | |
############## | |
# alter the default colors to make them a bit prettier | |
echo -en "\e]P0000000" #black | |
echo -en "\e]P1D75F5F" #darkred | |
echo -en "\e]P287AF5F" #darkgreen | |
echo -en "\e]P3D7AF87" #brown | |
echo -en "\e]P48787AF" #darkblue |
/* | |
* This first function maps shortcodes to their respective resources, | |
* then checks whether those shortcodes exist in the content, | |
* then stores the required resource handles in a custom field. | |
* This way, we aren't running resource-intensive functions on every page load. | |
*/ | |
function check_post_shortcodes($post_id) { | |
// Map conditional shortcodes to their respective resource handle | |
// Remember to manually dequeue resource handles below as well. |
#!/usr/bin/env sh | |
usage() { | |
echo "show-ansi-colors <n>" | |
exit 0 | |
} | |
(( $# < 1 )) && usage | |
show_ansi_colors() { |
While I'm learning how to use Nginx, I was instructed to update the server_names_hash_bucket_size
(/etc/nginx/nginx.conf
) value from 32 to 64, but I don't understand why should I increase the value to 64.
References that have been read so far: