diff --git a/Gemfile b/Gemfile index 12792d6..bd82b0a 100644 --- a/Gemfile +++ b/Gemfile @@ -17,6 +17,7 @@ gem 'minima', '~> 2.5' gem 'jekyll-include-cache' gem 'minimal-mistakes-jekyll' +gem 'jekyll-spaceship' group :jekyll_plugins do gem 'jekyll-feed', '~> 0.12' @@ -31,3 +32,5 @@ end # Performance-booster for watching directories on Windows gem 'wdm', '~> 0.1.1', platforms: %i[mingw x64_mingw mswin] + +gem "webrick", "~> 1.7" diff --git a/Gemfile.lock b/Gemfile.lock index 5756a43..c6d11b7 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -30,6 +30,7 @@ GEM faraday-rack (1.0.0) ffi (1.15.4) forwardable-extended (2.6.0) + gemoji (3.0.1) http_parser.rb (0.8.0) i18n (1.8.11) concurrent-ruby (~> 1.0) @@ -61,6 +62,11 @@ GEM jekyll (>= 3.8, < 5.0) jekyll-sitemap (1.4.0) jekyll (>= 3.7, < 5.0) + jekyll-spaceship (0.10.2) + gemoji (~> 3.0) + jekyll (>= 3.6, < 5.0) + nokogiri (~> 1.6) + rainbow (~> 3.0) jekyll-watch (2.2.1) listen (~> 3.0) kramdown (2.3.1) @@ -84,12 +90,16 @@ GEM jekyll-paginate (~> 1.1) jekyll-sitemap (~> 1.3) multipart-post (2.1.1) + nokogiri (1.14.0-x86_64-linux) + racc (~> 1.4) octokit (4.21.0) faraday (>= 0.9) sawyer (~> 0.8.0, >= 0.5.3) pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (4.0.6) + racc (1.6.2) + rainbow (3.1.1) rb-fsevent (0.11.0) rb-inotify (0.10.1) ffi (~> 1.0) @@ -105,6 +115,7 @@ GEM terminal-table (2.0.0) unicode-display_width (~> 1.1, >= 1.1.1) unicode-display_width (1.8.0) + webrick (1.7.0) PLATFORMS x86_64-linux @@ -113,11 +124,13 @@ DEPENDENCIES jekyll (~> 4.2.1) jekyll-feed (~> 0.12) jekyll-include-cache + jekyll-spaceship minima (~> 2.5) minimal-mistakes-jekyll tzinfo (~> 1.2) tzinfo-data wdm (~> 0.1.1) + webrick (~> 1.7) BUNDLED WITH 2.3.1 diff --git a/_config.yml b/_config.yml index bc016c1..1ffb948 100644 --- a/_config.yml +++ b/_config.yml @@ -41,7 +41,7 @@ defaults: read_time: true show_date: true comments: true - share: true + share: false related: true # _pages - scope: @@ -60,7 +60,7 @@ author: links: - label: "sahinakkayadev" icon: "fab fa-fw fa-github" - url: "https://github.com/sahinakkayadev" + url: "https://github.com/sahinakkaya" - label: "Asocia" icon: "fab fa-fw fa-stack-overflow" url: "https://stackoverflow.com/users/9608759" @@ -85,6 +85,7 @@ minimal_mistakes_skin: "neon" # "air", "aqua", "contrast", "dark", "dirt", "neon plugins: - jekyll-feed - jekyll-include-cache + - jekyll-spaceship # Exclude from processing. # The following items will not be processed, by default. diff --git a/_posts/2021-12-25-first-blog-post.md b/_posts/2021-12-25-first-blog-post.md index 393b7e1..2041746 100644 --- a/_posts/2021-12-25-first-blog-post.md +++ b/_posts/2021-12-25-first-blog-post.md @@ -21,7 +21,7 @@ So here I am and welcome to my first blog. Having a personal space on the Intern There are several reasons for starting my own site and blogging, but I can list the most important ones as follows: ### Giving back to community -I use the software developed and brought by the community every day. The moment I power on my computer I start using Free Software. It really amazes me to see the work produced by people who do not know each other at all. For example, I did not even write a single line of code for this site. If Free Software didn't exist, I'd either have to spend money and use a platform that I have limited control over, or waste my time and build a site with a possibly worse design than this one[*](## "swh"){: .cd}. In return for this, I want to give back to the community. For me, the way to give back to the community so far has been to share the projects I've done and archive the things I learn every day in a repository called [TIL](https://github.com/Asocia/til)[*](## "Today I Learned"){: .cd}. But some of the til's I've written recently are getting lengthy and I think they deserve their own posts. So instead of writing long til's, I will blog what I learned here. +I use the software developed and brought by the community every day. The moment I power on my computer I start using Free Software. It really amazes me to see the work produced by people who do not know each other at all. For example, I did not even write a single line of code for this site. If Free Software didn't exist, I'd either have to spend money and use a platform that I have limited control over, or waste my time and build a site with a possibly worse design than this one[*](## "swh"){: .cd}. In return for this, I want to give back to the community. For me, the way to give back to the community so far has been to share the projects I've done and archive the things I learn every day in a repository called [TIL](https://github.com/sahinakkaya/til)[*](## "Today I Learned"){: .cd}. But some of the til's I've written recently are getting lengthy and I think they deserve their own posts. So instead of writing long til's, I will blog what I learned here. ### Archiving the memories I like to go over what I have done in the past once in a while. Blogging is perfect way to do this. I still read my diaries that I wrote in the past and they are fun. But I promise I will keep these posts more formal than my diaries[*](## "swh"){: .cd}. diff --git a/_posts/2022-01-04-build-and-deploy-automatically.md b/_posts/2022-01-04-build-and-deploy-automatically.md index f19ebe7..66017f3 100644 --- a/_posts/2022-01-04-build-and-deploy-automatically.md +++ b/_posts/2022-01-04-build-and-deploy-automatically.md @@ -59,7 +59,7 @@ That's it! We have created our first Action. When we push this change, GitHub wi restore-keys: | ${{ runner.os }}-gems-{% endraw %} ``` -We are done with the Actions part. You can see the final code [here](https://github.com/Asocia/sahinakkayadotdev/blob/main/.github/workflows/jekyll.yml). When you are also done with the code, just push it to trigger the action. +We are done with the Actions part. You can see the final code [here](https://github.com/sahinakkaya/sahinakkayadotdev/blob/main/.github/workflows/jekyll.yml). When you are also done with the code, just push it to trigger the action. ### Setting up the Webhook and related endpoint Now that we set up our Action to build the site, we need to let our server know about the changes so that it can pull the changes. diff --git a/_posts/2023-01-16-hot-reloading-with-trap-and-kill.md b/_posts/2023-01-16-hot-reloading-with-trap-and-kill.md index 3abb3f4..07c1a6e 100644 --- a/_posts/2023-01-16-hot-reloading-with-trap-and-kill.md +++ b/_posts/2023-01-16-hot-reloading-with-trap-and-kill.md @@ -5,7 +5,6 @@ tags: trap kill linux --- ## `trap` them and `kill` them! - There is a beautiful command in Linux called [`trap`](https://man7.org/linux/man-pages/man1/trap.1p.html) which *trap*s signals and let you run specific commands when they invoked. There is also good ol' [`kill`](https://man7.org/linux/man-pages/man1/kill.1.html) command which not only kills processes but allows you to specify a signal to send. By combining these two, you can run specific functions from your scripts any time!