marc.fail

What’s inside the acces log?

NGINX logs all the resources a client (by IP) is accessing as well as status code and user agent and some more information. That’s what every web server does by default. The thing is with log retention. By default, logrotate.d is set t keep logs for 52 days. As my webserver is not running for so long in the moment as I’m constantly changing things, I just have no Idea if that’s true. I’ll have to test it.

But how to do statistic with a log file?

After some googling, I found a tool called goaccess. It is a command line based log file analyzer. As a little bonus, it can generate a report html file, which presents the log file data in a nice gui instead within the command line.

What happened?

I was wondering what happend. I think something inescapable that happened to other things before, too: when something is really amazing, kind of exclusive (or at least expensive) and becomes ‘hip’, people will also get a taste for it or at least believe that it’s good, because everybody else of their peer group likes it. So you go there on the weekend to treat yourself maybe. Of course that’s amazing!

Woah, that sounds stupid, how did you moron fix it?

Good question! The solution was simple, using a submodule, but it took me a while to figure it out. I created another empty folder on my local machine and git clone’d the theme’s repo into it.

Okay, but how did you bring this separate repo to your weblog’s repo?

That was also easy. cd to the /themes/ folder of hugo and run git submodule add https://github.com/wortkrieg/ .git git submodule update