This is a short and simple example on how to build a proper Keycloak cluster, using DNS_PING as discovery protocol and an NGINX server as reverse proxy.
If you prefer to use JDBC_PING, see @xgp's example gist here: https://gist.github.com/xgp/768eea11f92806b9c83f95902f7f8f80
Please see also my video about Keycloak Clustering: http://www.youtube.com/watch?v=P96VQkBBNxU
NOTE: The video covers JDBC_PING protocol and uses the legacy Keycloak Wildfly distribution!
| openssl req -x509 -new -key octopus.key -days 3650 -subj "/C=GB/ST=YourState/L=YourCity/O=Your Company/OU=Department/CN=${fqdn}" | | |
| openssl pkcs12 -export -inkey octopus.key -passout pass: | | |
| openssl base64 |
Kafka Binary files : http://kafka.apache.org/downloads.html
Atleast 2 AWS machines : AWS EMR or EC2 will be preferable
A Kafka Manager Utility to watch up the Cluster : https://cwiki.apache.org/confluence/display/KAFKA/Ecosystem
| #!/bin/bash | |
| ## Fix OneDrive for Mac CPU usage | |
| ## | |
| ## Seems this is still a problem 5 years later after I created this little gist. | |
| ## I have long since stopped using OneDrive (luckily), but according to | |
| ## comments below, I have added the new path for OfficeFileCache for macOS | |
| ## Mojave (10.14) and Catalina (10.15). | |
| ## Run this on macOS Mojave (10.14) and Catalina (10.15) | |
| find ~/Library/Containers/ -type d -name OfficeFileCache -exec rm -r {} + |
