Solita Developer Blog
CSS HTML JavaScript Ruby Shell
Switch branches/tags
Nothing to show
Pull request Compare This branch is 76 commits behind solita:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Here are some developer-oriented thoughts from Solita Oy. Our stories have not yet been told. More will come. Stay tuned at


We use a combination of Jekyll and Github Pages to run the site.

If you want to write a post, here's how:

  1. Fork this project to yourself (upper right corner)
  • You need a Github account to do this
  1. Clone your own fork to your computer (git clone)
  2. Add your author info to _config.yml
  • The email value is a MD5 hash of your email
  1. Write a new post under the _posts folder using Markdown, look at other posts for example of what to write there
  2. If you have Ruby and Jekyll, preview your post locally (instructions below)
  3. Create a pull request at
  • Choose your fork on the right
  • Write some info about the post
  1. Wait for comments and publish!

Optional: Adding exact publication time to your post

Normally the publication date of a post is read from the filename of the post (, e.g. In this case the puslishing time will show up as 00:00:00.

If you want to specify the exact time your post was published, you can add a date-field to your post. In the date field you can specify the publication time in the format YYYY-MM-DD HH:MM:SS +/-TTTT.

For example:

date: 2016-04-25 13:30:00 +0200

Previewing posts

You need Ruby and Jekyll if you want to preview your posts locally on the blog. If you're fine with just previewing the Markdown, you can use a Markdown preview script, like this one for Sublime Text.

Option A, Running solita-blag dockerized extravaganza

Super-fast, live-reload for posts, sass and templates.

  1. You have docker installed? Right?
  2. Run docker/, this can take a while but should be run only once
  3. Run docker/, keep it running, stop with ctrl+c
  4. Head to http://localhost:4444
  5. Edit post with your favourite editor and check changes via browser

Next time when conjuring new post, only docker/ should do it.


docker rmi solita-blag -> Delete image docker/ -> Opens bash to container without starting jekyl and compass

Windows? Help wanted!

Option B, Running a vagrant virtual machine (standardized environment)

  1. Install Vagrant
  2. Install Virtualbox
  3. cd vagrant
  4. vagrant up blag
  5. Wait patiently as the ruby goodness is downloaded and configured
  6. http://localhost:4444 now should serve your version of the blog

If anything goes wrong, good luck. vagrant ssh blag and try figure it out.

When you're done you might want to shutdown the virtual machine. vagrant destroy or something like that.

Option C, Installing Ruby on your workstation

For Windows, download & install the latest Ruby 2.x and Development Kit from

Note: Make sure to tick the checkbox "Add Ruby to PATH" (or something). You can also try:

For Debian (Jessie), the easiest path seems to be:

  1. sudo apt-get install bundler zlib1g-dev
  2. bundle install
  3. bundle exec jekyll serve --watch

For OSX, use the instructions below. If you have installed Xcode, you might have ruby already. No guarantees about this working with that so use RVM

  1. curl -L | bash -s stable --ruby=2.2.1
  2. fork this repo
  3. go to your working copy of
  4. rvm use 2.2.1
  5. verify that 2.2.1 used by ruby -v (On linux you might need to fix gnome-termina:
  6. gem install bundler
  7. Run bundle install for depencies
  8. Make sure the installation succeeds
  9. Type in: bundle exec foreman start
  10. Open browser to: http://localhost:4000/


For development, you need Ruby and Jekyll. If you want to tweak the CSS, you need Compass. Also, if you want to make stuff easier, install foreman.

  1. Install Ruby (above)
  2. Go to your cloned copy of
  3. To install Jekyll, Compass and foreman, type into a command prompt or terminal: bundle install
  4. Make sure the install succeeds
  5. Type in: bundle exec foreman start
  6. Jekyll and Compass should start!

Updating to Jekyll 3

Note: This concerns only people who forked this repo when it was still running Jekyll 2 (prior to 25.4.2016).


GitHub has recently moved from using Jekyll 2 to Jekyll 3. Starting from 1.5.2016 GitHub will only support Jekyll 3, so this repository has been updated to use the new version also.

If you're interested in the changes the update brings, you can read about them here The way posts are written does not change at all, so for a blog author the changes are practically unnoticable.

Update instructions

First thing to do is to synch your fork with the changes in the main repository. If you don't know how to do this, GitHub has good instructions. First you need to add the main repository as a remote ( after which you can sync your fork (

Option A, if you're using Vagrant

If you're using Vagrant, you're already done! Just start vagrant with vagrant up blag like before.

Option B, if you're using Ruby

Jekyll 3 only supports Ruby 2. First check which version you have with ruby -v.

If already have Ruby 2.x, simply update the local gems with bundle update.

If you currently have Ruby 1.x, you must first install Ruby 2 and then install the packages in the gemfile. For Windows, you can get Ruby 2 from For OSX, you can install Ruby 2 with RVM:

  1. rvm install 2.2.1
  2. rvm use 2.2.1
  3. gem install bundler
  4. bundle install

Technology stack

/dev/solita is built using all the hippiest hip technologies available:

git, Github Pages, Ruby, Jekyll, Markdown, Sass, Compass, foreman, jQuery, Gravatar, disqus, Google Analytics, AddThis