Martin Vích's blog

How to instal Elasticsearch and Kibana on Docker

Martin Vích

Elasticsearch and Kibana are pretty popular way to store, visualise and analyze data from your application. In this post I want to provide a fast and easy guide how to setup Elasticsearch and Kibana on Docker. I will not go deep with each parameter explanation since I don't want begginers to be flooded with stuff they don't need or understand.

Pretty much the only requirement is to have Docker installed.

First step is pulling Elasticsearch and Kibana images.

docker pull docker.elastic.co/elasticsearch/elasticsearch:7.6.2
docker pull docker.elastic.co/kibana/kibana:7.6.2

Second step is to create network for our containers because Kibana needs to be able to connect to Elasticsearch to get data it needs. In official docs you can see how to skip this stepp using --link parameter but that parameter is deprecated and can be removed anytime.

docker network create elastic

Then we create containers.

docker container create -p 9200:9200 -p 9300:9300 --name=elasticsearch --network=elastic -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:7.6.2
docker container create --name=kibana --network=elastic -p 5601:5601 docker.elastic.co/kibana/kibana:7.6.2

Finally only thing we just need to start both containers. After a minute just go to localhost:5601.

docker start elasticsearch
docker start kibana

And we should see the result

Advanced git commands

Martin Vích

I'm just going to store this here for my personal usage...

Reset

Resets state of branch to origin/branch. The --hard option throws away any changes, --soft only moves HEAD, keeping the changes.

git reset --hard origin/mybranch

Revert

Reverts certain commit. Allows saving "revert" as separate commit which keeps the changes it in the history. The -m option specifies which side of merge should be kept. 1 means parent branch (So for example if you want to revert feature branch merge into develop then 1 is keep develop changes).

git revert -m 1 commithash

Reverting last commit

git revert HEAD

Rebase

Resolves conflicts by rebasing branch onto another branch. Has -i option which enters interactive mode that allows editing commit messages, squashing commits and other stuff.

git rebase -i develop

Push -u

When working on branch that doesn't have an upstream branch things can be made quicker with this command. Creates upstream branch with same name and pushes the changes into it.

git push -u

Must have pust.default current option set

git config --global push.default current

How to install Ruby on Rails on Mac

Martin Vích

Install homebrew
run xcode-select --install
Install & init rbenv with brew install rbenv && brew install rbenv && rbenv init
List available ruby versions with rbenv install -l
Install preferred version with rbenv install 2.5.1
Check installed versions with rbenv versions. There should be "system" and your installed version.
Set version you want to use with rbenv global 2.5.1
Verify with ruby -v
Ensure that rbenv will be automatically run by adding eval "$(rbenv init -)" to your ~/.bash_profile
Profit!

Using git on Windows

Martin Vích

Motivation

For a long time I was using Visual Studio with TFS to control my code. So when company I was working at that time wanted to move to git I continued to use integreated tools as well. And in a small team it was fine, basicly I couldn't tell the difference from TFS. But then I moved to other company with larger team that was starting to use Gitflow and Visual Studio tools started to get painfull to use. I started to use Atlassian SourceTree but after they had a streak of several patches that caused massive lagging of that application I decided that it's time to try out using command line git. It was rough at the beginning since I was never much of a command line user but after some time and some tweaking it became my preffered way of using Git on Windows.

Tools

I'm using Powershell but you can use any shell you like. As a console I'm using ConEmu for Visual Studio projects and build in terminal for Visual Studio Code. Here's list of tools and plugins I found are worth using

ConEmu- alternative advanced console for Windows. It has much better features than cmd and is better with displaying colors than PowerShellISE.
Credential Manager for Windows - Utility that will store git credentials to Windows credential store so there is no need to provide them for each operation with the remote. It has great support for all main git repositoriies. It even supports multi factor authetication with Visual Studio Team Services if you're using it (you should be doing that whenever it's possible)
PsGet - PowerShell module installer. This is optional I use it to install PS plugins but you can do that manually
Posh-git - PowerShell module that displays current branch. This is great plugit that will show you on which branch you're currently working on, branch sync status and how many file changes have you made since last commit
PSReadLine - Powershell module that will add autocomplete to git so you don't have to write whole branch names etc

Installation

Install ConEmu
Open ConEmu, go to settings window. There in \Startup\Tasks add a new task (+ button), name it Powershell and set command as Powershell.exe. Then go to the \Startup and in the startup options select Specified named task\Powershell. This will set Powershell console as the default one.
If you don't want to install PowerShell modules manually install PsGet.
Install Posh-git with command PowerShellGet\Install-Module posh-git -Scope CurrentUser
Update Posh-git with command Update-Module posh-git
Add Posh-git to your profile with command Add-PoshGitToProfile
Install PSReadLine with command Install-Module PSReadLine
Go to your Documents folder and from there to WindowsPowerShell. There will be Microsoft.PowerShell_profile.ps1. Open it in file editor and add:

\# Load posh-git example profile
. 'C:\Users\{your user name}\Documents\WindowsPowerShell\Modules\posh-git\profile.example.ps1'

\# Load PSReadline
if ($host.Name -eq 'ConsoleHost') {
  Import-Module PSReadline
}

This will automatically load your plugins when you start new Powershell window

Install Git Credential Store utility
Restart ConEmu. Now when you're at a location which is a git repository, you should see a branch name at the end of the line. It's colors are explained at posh-git readme. It will look like this:

C:\Users\mvich\Source\Repos\myproject [develop]>

Paged index with Wyam.io

Martin Vích

I've decided to create new blog to share experiences I have with various peaces of software and since I'm doing a lot of .NET development Wyam.io project caught my eye. It comes with everything I expected to need for a "begginers" blogging tool so I decided to give it a try.

It's really easy to use but there was one thing that I wanted to adjust. And that is how "index" page works by default. I didn't want it to show first few top post but instead I want it to have paging itself, not just on archive page. Using paginate in a separate pipeline is quite easy but problem is that you cannot just copy input/index.cshtml from the pagination example into your root index.cshtml. That would break your pipelines from the blog recipe.

Fortunately with just few adjustments it's possible to make it work that way.

Config.wyam

First we'll make some changes to config.wyam. We need to create a setting for the number of posts per page and also add new pipeline that will be responsible for creating paged index.

Settings["PostsPerPage"] = 3;

Pipelines.Add("Archive",
    ReadFiles("index.cshtml"),
    Paginate(3,
        Documents(BlogPipelines.Posts),
        OrderBy((doc, ctx) => doc.Metadata.Get<DateTime>("Published"))
    ),
    Razor(),
    WriteFiles(string.Format("{0}.html", @doc.Get<int>("CurrentPage")))
);

Index.cshtml

Now configuration is done and we can move to the index file. We could copy posts index into application root but problem with that is that the Blog template won't work anymore since the new index file expects pagination metedata which Blog pipelines aren't providing. Also the example index doesn't use _Layout and other things we probably want to keep. So instead let's copy index from the CleanBlog theme and add paging there.

First we'll focus on the part where the posts are rendered

@{
    int page = Model.ContainsKey("CurrentPage") ? Model.Get<int>("CurrentPage") : 1;
    int postsPerPage = Context.Get<int>("PostsPerPage");
    int totalPages = (Documents[BlogKeys.Posts].Count() / postsPerPage) + ((Documents[BlogKeys.Posts].Count() % postsPerPage) > 0 ? 1 : 0);
    bool first = true;
    foreach(IDocument doc in Documents[BlogKeys.Posts].Skip((page - 1) * postsPerPage).Take(postsPerPage))
    {
        // You don't have to change individual posts rendering
    }
}

This will ensure that when index file gets processed by Blog pipeline it will have reasonable default metadata and won't throw any exception.

Once that's done the only thing left is to add navigation between pages. You can add it right after the post rendering block

    <div>
        @for(int p = 1 ; p <= totalPages ; p++)
        {
            <span>
                @if(p == page)
                {
                    <strong>Page @p</strong>
                }   
                else
                {
                    string pageLink = p == 1 ? "/" : p.ToString();
                    <a href="@pageLink">Page @p</a>
                }
                &nbsp;&nbsp;
            </span>
        }
    </div>

This will add Page 1 to Page N links under your posts. You can also adjust this logic to show Older / New posts links.

I hope that this will help you with adjusting your Wyam site.