| #/bin/bash | |
| NAME="$1" | |
| if [ -z "$NAME" ]; then | |
| echo "usage: create-libvirt.sh <name>" | |
| exit 1 | |
| fi | |
| CLUSTER_DIR="$HOME/clusters/${NAME}" | |
| if [ -d "$CLUSTER_DIR" ]; then |
RUN apt update
RUN apt upgrade -y
RUN apt install -y apt-utils
RUN a2enmod rewrite
RUN apt install -y libmcrypt-dev
RUN apt install -y libicu-dev
RUN docker-php-ext-install -j$(nproc) intl
RUN apt-get install -y libfreetype6-dev libjpeg62-turbo-dev libpng12-dev
RUN docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/
| # Use this script to test that your Telegram bot works. | |
| # | |
| # Install the dependency | |
| # | |
| # $ gem install telegram_bot | |
| # | |
| # Run the bot | |
| # | |
| # $ ruby bot.rb | |
| # |
| #!/bin/sh | |
| # | |
| # Usage: whenever.sh [pattern] [command] | |
| # | |
| # Executes a command whenever files matching the pattern are closed in write | |
| # mode. "{}" in the command is replaced with the matching filename (via xargs). | |
| # Requires inotifywait from inotify-tools. | |
| # | |
| # For example, |
| ``` | |
| ## Master-1 | |
| create database replica_db; | |
| create user 'slave'@'10.10.22.104' identified by 'abc@123'; | |
| create user 'slave'@'10.10.22.105' identified by 'abc@123'; | |
| grant replication slave on *.* to 'slave'@'10.10.22.104' identified by 'abc@123'; | |
| grant replication slave on *.* to 'slave'@'10.10.22.105' identified by 'abc@123'; | |
| vi /etc/my.cnf.d/mariadb-server.cnf | |
| [mariadb] |
| #!/bin/bash | |
| # PARAM | |
| mysql_master=<%= @DBMY_MASTER_HOST %> | |
| user_mysql=root | |
| password_user_mysql=<%= @USER_ROOT_DBMY_SLAVE_PASSWORD %> | |
| replication_user=<%= @REP_USER %> | |
| replication_password=<%= @REP_PASSWORD %> | |
| read -p "Etes vous sur de vouloir installer la replication ? [Y/N]" -n 1 -r |
| REFERENCE: | |
| http://hzcsky.blog.51cto.com/1560073/479476 | |
| # $Id: mysql-replication 335 2005-10-13 19:46:20Z sbalukoff $ | |
| # To set up bi-directional mysql replication: | |
| # For the purposes of this document, we have two servers which will in the | |
| # end be filling a co-master type relationship. However, since when you set up | |
| # this replication there will probably be one machine with all the data on it | |
| # that needs to be brought into sync with the other machine, the machine |
| #!/bin/sh | |
| SSH_PUBLIC_KEY='insert_your_ssh_public_key_here' | |
| function add_ssh_public_key() { | |
| cd | |
| mkdir -p .ssh | |
| chmod 700 .ssh | |
| echo "$SSH_PUBLIC_KEY" >> .ssh/authorized_keys | |
| chmod 600 .ssh/authorized_keys |