Update favicon and getting ready

This commit is contained in:
cool-mist 2020-12-08 16:32:41 +00:00
parent 23ab9cd994
commit 9439035bc5
2 changed files with 19 additions and 10 deletions

View File

@ -3,27 +3,29 @@ layout: post
title: Getting Ready
---
After contemplating about different options for DNS, hosting, and the bloggging technology for more than a week, I have settled on the following configurations to start blogging! (for now! )
![favicon]({{ site.baseurl | absolute_url }}/public/favicon.png)
### DNS
After contemplating about different options for hosting, blogging technologies and domain names for a couple of days, I have settled on the following configurations to start blogging! (for now! )
[Bionic Beanie](https://theportalwiki.com/wiki/Bionic_Beanie) is a head wear from [Portal 2](https://en.wikipedia.org/wiki/Portal_2) co-op. Portal series is one of my favourite PC games and Bionic Beanic Blog scores 10/10 on alliteration consonance (in my opinion :P)
### Domain Name
[Bionic Beanie](https://theportalwiki.com/wiki/Bionic_Beanie) is a head wear from [Portal 2](https://en.wikipedia.org/wiki/Portal_2) co-op. Portal series is one of my favourite PC games and **Bionic Beanie Blog** sounded great in my head ([alliteration](https://en.wikipedia.org/wiki/Alliteration) skills bruh!).
Bought it right away from [Go Daddy](https://in.godaddy.com/). The package included DNS hosting as well.
### Blog
### Blog Tech
I wanted to use a static site generator as opposed to any CMS. In my experience, CMSes typically get bloated with more plugins and addons and tend to get slower. [Jekyll](https://jekyllrb.com/) is what I settled with - mainly because I recognise the name Jekyll from my childhood with [**The Strange Case of Dr Jekyll and Mr Hyde**](https://en.wikipedia.org/wiki/Strange_Case_of_Dr_Jekyll_and_Mr_Hyde). Also, Jekyll is highly configurable and blazing fast!!
I wanted to use a static site generator as opposed to any CMS like Wordpress. They should be faster and easier to configure/manage. [Jekyll](https://jekyllrb.com/) is what I settled with - mainly because I [recognise the name from my childhood](https://en.wikipedia.org/wiki/Strange_Case_of_Dr_Jekyll_and_Mr_Hyde).
To start things off, this site is powered by [Lanyon](https://github.com/poole/lanyon#readme) which is an extension of [Poole](https://getpoole.com/) - the Jekyll butler (name derived from the afore mentioned book).
To fasttrack my site design, I decided to use [Lanyon](https://github.com/poole/lanyon#readme) which is an extension of [Poole](https://getpoole.com/) - which I also [recognize from my childhood](https://study.com/academy/lesson/mr-poole-in-dr-jekyll-mr-hyde.html).
### Hosting
### Hosting my blog
Bought the cheapest VPS from [Vultr](https://www.vultr.com/) for $5 a month - 1GB RAM and a single core shared server. This is good enough for hosting my static files.
Bought the cheapest VPS from [Vultr](https://www.vultr.com/) for $5 a month - 1GB RAM and a single core shared server. This is more than good enough for hosting my static files. I might end up using this instance for some of my other projects too.
### The Setup
### Working Setup
The server will run behind an [nginx](https://www.nginx.com/) instance serving static files from `_site` folder that are built as part of jekyll build process. This way, to publish new changes, I just have to clone and build the files. The blog itself will be in a private git repository.
The server will run behind an [nginx](https://www.nginx.com/) instance serving static files from `_site` folder that are built as part of jekyll build process. This way, I just have to clone and build the files to publish new changes. I will push the blog site data to a remote git repository to manage the articles.
[LetsEncrypt](https://letsencrypt.org/) helped issuing free ssl cert for my domain.
@ -46,4 +48,11 @@ And publish new changes with `JEKYLL_ENV="production" bundle exec jekyll build`
It should be possible to do this with a git hook, but I'm not too worried about it right now.
### Logo
The letters signify the first letter of the site's name. The color scheme is a reference to the two different portal colors in Portal.
![favicon]({{ site.baseurl | absolute_url }}/public/favicon.png)
**Let's Go**

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.9 KiB

After

Width:  |  Height:  |  Size: 1.1 KiB