Explore >> Select a destination
|
You are here 
|
codeinthehole.com | ||
| | | | |
endot.org
|
|
| | | | | For a while now, I've been backing up the few WordPress blogs that I run for various people with a very simple script that followed this algorithm: Copy files to a temporary directory. Dump the MySQL data into a file in that directory. Tarball it up. Scp that file to another server that I run. At the time, I did this because it was the simplest thing that could possibly work. | |
| | | | |
bobby-tables.com
|
|
| | | | | ||
| | | | |
fak3r.com
|
|
| | | | | ||
| | | | |
arveknudsen.com
|
|
| | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. This is generally known as the ELK stack, which stands for Elasticsearch, Logstash (precursor to Fluentd) and Kibana. | ||
