๐ง๐ท ๐ฎ๐น #DBRE #databases #docker #deployment #automation #aws #gcp #cloud #ansible #terraform #wine #coffee โ
-
[BIANCHI.LABS]
- I'm based in Brazil
-
08:22
(UTC -03:00) - http://www.wagnerbianchi.com
- in/wagnerbianchi
Pinned Loading
-
bianchi_postgresql_docker_image
bianchi_postgresql_docker_image PublicMy docker images for PostgreSQL.
Dockerfile
-
Ansible-AWS-MariaDB
Ansible-AWS-MariaDB PublicThree roles to give you a complete VPC, three MariaDB Servers in Replication, and a MaxScale w/ MariaDBMon and ReadWriteSplit.
Shell
-
Ansible-AWS-MariaDB (roles execution)
Ansible-AWS-MariaDB (roles execution) 1[BIANCHI LABS - ansible] ansible@jumphost: roles $ ansible-playbook bianchi-aws-bootstrap/bianchi-aws-bootstrap.yml
23PLAY [localhost] ****************************************************************************************************************************
45TASK [Gathering Facts] **********************************************************************************************************************
-
MaxScale 2.2.X setup (MariaDBMon+Rea...
MaxScale 2.2.X setup (MariaDBMon+ReadWriteSplit Router) 1#: This gist is supposed to be used when someone else intends to have a simple Maxscale 2.2.X++ setup
2#: considering a replication cluster. By replication cluster I mean one master and X slaves; in the
3#: case of this gist, I'm using just one slave, but, you can add as many as you want to add more to the
4#: below gist. You will notice that Maxscale after setup will be configured using dynamic commands and
5#: that is the place you will adjust your servers to be created an added to the service+monitor that
-
MAXSCALE_SETUP_RWSPLIT_GALERAMON
MAXSCALE_SETUP_RWSPLIT_GALERAMON 1#: This gist is supposed to be used when someone else intends to have a simple Maxscale 2.2.X++ setup
2#: considering a MariaDB Cluster. The service has a listener, here, allocated the mysql/3306 port.
34###################### SETUP MARIADB OFFICIAL REPO AND MAXSCALE PACKAGES ######################
5
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.