en <![CDATA[Project Nine]]> https://blog.projectnine.com/ Ghost 0.6 Sun, 17 Dec 2017 16:47:21 GMT 60 <![CDATA[Setting Up Fail2Ban With ELK]]> One of the first things I wanted to do with my ELK stack (Elasticsearch, Logstash and Kibana) was import Fail2Ban logs. Here is how I made it happen on a Debian based system.

Setting up Logstash-forwarder

Unfortunately, the logs for fail2ban are set the local machine's time and don't include

]]> http://tracking.feedpress.it/link/4086/569682 d206f19d-7456-49da-adb9-225b798ede32 Tue, 10 Feb 2015 01:12:04 GMT

One of the first things I wanted to do with my ELK stack (Elasticsearch, Logstash and Kibana) was import Fail2Ban logs. Here is how I made it happen on a Debian based system.

Setting up Logstash-forwarder

Unfortunately, the logs for fail2ban are set the local machine's time and don't include the timezone:

2015-02-08 09:28:52,438 fail2ban.actions: WARNING [ssh] Ban XX.XX.XX.XX

To get around this, when configuring logstash-forwarder (/etc/logstash-forwarder), make sure to include the correct timezone.

service logstash-forwarder reload

Setting up Logstash

Create a new configuration file for fail2ban in /etc/logstash/conf.d If your ELK server(s) are not located in the same timezone as the other servers, make sure to add which timezones you need. Aside: let me know if this possible using variables.

We are using some custom patterns so next, create the directory /etc/logstash/patterns and add the following.

service logstash force-reload

The Dashboard

Here is a Kibana dashboard config for fail2ban to get you started. Let me know on twitter if you have any issues.

Setting Up Fail2Ban With ELK

]]> <![CDATA[Ghost]]>

I’m going to use @tryghost for my next blog. There is nothing wrong with #WordPress, but I’m digging the simplicity of #ghost

— Justin Braithwaite (@nonameplayer) November 18, 2013

That was just over 24 hours ago. I have since spun up a new VPS on Linode, set up

]]> http://tracking.feedpress.it/link/4086/569683 0a883946-6aee-4a7c-b041-81c78c682eef Tue, 19 Nov 2013 12:00:00 GMT

I’m going to use @tryghost for my next blog. There is nothing wrong with #WordPress, but I’m digging the simplicity of #ghost

— Justin Braithwaite (@nonameplayer) November 18, 2013

That was just over 24 hours ago. I have since spun up a new VPS on Linode, set up Ghost with a reverse proxy from nginx and things are generally working.

There is a lot to like about this new blogging platform: it's ambitious, the interface is best-in-class and it is lightning fast out of the box. That said, it will be a while before it can dethrone the king.

Ghost needs to be much easier to install. One of the reasons WordPress is so ubiquitous is that practicaly every shared hosting environment supports PHP and MySQL. Since Ghost is based on node.js, you have three ways to get it running:

  1. Self-host — which means you will need ssh access and the ability to install node.js via a CLI.
  2. Deploy directly to a supported cloud service using an installer.
  3. Have Ghost host the site for you (currently not available)

Besides installation issues, some of the blogging basics are missing and I have already encountered a few major issues.

The fact that you are reading this blog post—which is currently being servered using Ghost—is evidence of faith in an exciting new blogging platform.

Are your ready to take the plunge?

]]>