typo fixes and improvements

Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED
blog: how to grow lilies
2026-07-04 07:40:09 +05:30 · 2024-12-02 01:59:21 +05:30 · 2024-12-02 01:49:41 +05:30 · 2024-09-26 13:02:44 +05:30 · 2024-09-25 21:43:18 +05:30 · 2024-09-25 20:39:32 +05:30
199 changed files with 14017 additions and 10929 deletions
@@ -1,60 +0,0 @@
-# Sample workflow for building and deploying a Hugo site to GitHub Pages
-name: Deploy Elm site to Pages
-
-on:
-  # Runs on pushes targeting the default branch
-  push:
-    branches: ["main"]
-
-  # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
-
-# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-# Allow one concurrent deployment
-concurrency:
-  group: "pages"
-  cancel-in-progress: true
-
-# Default to bash
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  # Build job
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download and install elm
-        run: |
-          curl -L -o elm.gz https://github.com/elm/compiler/releases/download/0.19.1/binary-for-linux-64-bit.gz
-          gunzip elm.gz
-          sudo mv elm /usr/bin/elm
-          sudo chmod +x /usr/bin/elm
-      - name: checkout
-        uses: actions/checkout@v3
-      - name: build
-        run: elm make src/Main.elm --output public/app.js --optimize
-      - name: copy content for seving
-        run: cp -a content public/content 
-      - name: Upload artifact
-        uses: actions/upload-pages-artifact@v1
-        with:
-          path: public/
-
-  # Deployment job
-  deploy:
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    runs-on: ubuntu-latest
-    needs: build
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v1
@@ -0,0 +1,37 @@
+# Sample workflow for building and deploying a Hugo site to GitHub Pages
+name: Check build
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+  pull_request:
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Default to bash
+defaults:
+  run:
+    shell: bash
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+          cache: "npm"
+          cache-dependency-path: ./package-lock.json
+      - name: Setup Hugo
+        uses: peaceiris/actions-hugo@v2
+        with:
+          hugo-version: '0.134.3'
+          extended: true
+      - name: Install elm-land and node packages
+        run: npm install
+      - name: build
+        run: make
@@ -1,4 +1,13 @@
-# elm-package generated files
-elm-stuff
-# elm-repl generated files
-repl-temp-*
+/dist
+/.elm-land
+/.env
+/elm-stuff
+/node_modules
+.DS_Store
+*.pem
+/static/main.css
+/temp
+/blog/public
+/blog/node_modules
+.idea
+.vscode
@@ -0,0 +1,27 @@
+# build everything for production
+all: css build
+	@echo "--- production build finished"
+
+# build only css for production
+css:
+	@echo "--- building tailwind css"
+	npx tailwindcss -i ./src/input.css -o ./static/main.css --minify
+
+# compile only elm for production
+build:
+	@echo "--- compiling elm land project"
+	npx elm-land build
+	hugo --source blog --destination ../dist --minify
+
+# compile and watch for dev
+elm-serve:
+	npx elm-land server
+
+# build css and watch
+css-serve:
+	npx tailwindcss -i ./src/input.css -o ./static/main.css --watch
+
+# clean
+clean:
+	rm -rf dist
+	rm -rf blog/public
@@ -0,0 +1,2 @@
+# My Personal Website and Blog
+
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Avinal Kumar
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
@@ -0,0 +1,5 @@
+++
+title = '{{ replace .File.ContentBaseName "-" " " | title }}'
+date = {{ .Date }}
+draft = true
+++
@@ -0,0 +1,541 @@
+/*
+! tailwindcss v3.3.6 | MIT License | https://tailwindcss.com
+*/
+
+/*
+1. Prevent padding and border from affecting element width. (https://github.com/mozdevs/cssremedy/issues/4)
+2. Allow adding a border to an element by just adding a border-width. (https://github.com/tailwindcss/tailwindcss/pull/116)
+*/
+
+*,
+::before,
+::after {
+  box-sizing: border-box;
+  /* 1 */
+  border-width: 0;
+  /* 2 */
+  border-style: solid;
+  /* 2 */
+  border-color: #e5e7eb;
+  /* 2 */
+}
+
+::before,
+::after {
+  --tw-content: '';
+}
+
+/*
+1. Use a consistent sensible line-height in all browsers.
+2. Prevent adjustments of font size after orientation changes in iOS.
+3. Use a more readable tab size.
+4. Use the user's configured `sans` font-family by default.
+5. Use the user's configured `sans` font-feature-settings by default.
+6. Use the user's configured `sans` font-variation-settings by default.
+*/
+
+html {
+  line-height: 1.5;
+  /* 1 */
+  -webkit-text-size-adjust: 100%;
+  /* 2 */
+  -moz-tab-size: 4;
+  /* 3 */
+  -o-tab-size: 4;
+     tab-size: 4;
+  /* 3 */
+  font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, "Noto Sans", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";
+  /* 4 */
+  font-feature-settings: normal;
+  /* 5 */
+  font-variation-settings: normal;
+  /* 6 */
+}
+
+/*
+1. Remove the margin in all browsers.
+2. Inherit line-height from `html` so users can set them as a class directly on the `html` element.
+*/
+
+body {
+  margin: 0;
+  /* 1 */
+  line-height: inherit;
+  /* 2 */
+}
+
+/*
+1. Add the correct height in Firefox.
+2. Correct the inheritance of border color in Firefox. (https://bugzilla.mozilla.org/show_bug.cgi?id=190655)
+3. Ensure horizontal rules are visible by default.
+*/
+
+hr {
+  height: 0;
+  /* 1 */
+  color: inherit;
+  /* 2 */
+  border-top-width: 1px;
+  /* 3 */
+}
+
+/*
+Add the correct text decoration in Chrome, Edge, and Safari.
+*/
+
+abbr:where([title]) {
+  -webkit-text-decoration: underline dotted;
+          text-decoration: underline dotted;
+}
+
+/*
+Remove the default font size and weight for headings.
+*/
+
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+  font-size: inherit;
+  font-weight: inherit;
+}
+
+/*
+Reset links to optimize for opt-in styling instead of opt-out.
+*/
+
+a {
+  color: inherit;
+  text-decoration: inherit;
+}
+
+/*
+Add the correct font weight in Edge and Safari.
+*/
+
+b,
+strong {
+  font-weight: bolder;
+}
+
+/*
+1. Use the user's configured `mono` font-family by default.
+2. Use the user's configured `mono` font-feature-settings by default.
+3. Use the user's configured `mono` font-variation-settings by default.
+4. Correct the odd `em` font sizing in all browsers.
+*/
+
+code,
+kbd,
+samp,
+pre {
+  font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace;
+  /* 1 */
+  font-feature-settings: normal;
+  /* 2 */
+  font-variation-settings: normal;
+  /* 3 */
+  font-size: 1em;
+  /* 4 */
+}
+
+/*
+Add the correct font size in all browsers.
+*/
+
+small {
+  font-size: 80%;
+}
+
+/*
+Prevent `sub` and `sup` elements from affecting the line height in all browsers.
+*/
+
+sub,
+sup {
+  font-size: 75%;
+  line-height: 0;
+  position: relative;
+  vertical-align: baseline;
+}
+
+sub {
+  bottom: -0.25em;
+}
+
+sup {
+  top: -0.5em;
+}
+
+/*
+1. Remove text indentation from table contents in Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=999088, https://bugs.webkit.org/show_bug.cgi?id=201297)
+2. Correct table border color inheritance in all Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=935729, https://bugs.webkit.org/show_bug.cgi?id=195016)
+3. Remove gaps between table borders by default.
+*/
+
+table {
+  text-indent: 0;
+  /* 1 */
+  border-color: inherit;
+  /* 2 */
+  border-collapse: collapse;
+  /* 3 */
+}
+
+/*
+1. Change the font styles in all browsers.
+2. Remove the margin in Firefox and Safari.
+3. Remove default padding in all browsers.
+*/
+
+button,
+input,
+optgroup,
+select,
+textarea {
+  font-family: inherit;
+  /* 1 */
+  font-feature-settings: inherit;
+  /* 1 */
+  font-variation-settings: inherit;
+  /* 1 */
+  font-size: 100%;
+  /* 1 */
+  font-weight: inherit;
+  /* 1 */
+  line-height: inherit;
+  /* 1 */
+  color: inherit;
+  /* 1 */
+  margin: 0;
+  /* 2 */
+  padding: 0;
+  /* 3 */
+}
+
+/*
+Remove the inheritance of text transform in Edge and Firefox.
+*/
+
+button,
+select {
+  text-transform: none;
+}
+
+/*
+1. Correct the inability to style clickable types in iOS and Safari.
+2. Remove default button styles.
+*/
+
+button,
+[type='button'],
+[type='reset'],
+[type='submit'] {
+  -webkit-appearance: button;
+  /* 1 */
+  background-color: transparent;
+  /* 2 */
+  background-image: none;
+  /* 2 */
+}
+
+/*
+Use the modern Firefox focus style for all focusable elements.
+*/
+
+:-moz-focusring {
+  outline: auto;
+}
+
+/*
+Remove the additional `:invalid` styles in Firefox. (https://github.com/mozilla/gecko-dev/blob/2f9eacd9d3d995c937b4251a5557d95d494c9be1/layout/style/res/forms.css#L728-L737)
+*/
+
+:-moz-ui-invalid {
+  box-shadow: none;
+}
+
+/*
+Add the correct vertical alignment in Chrome and Firefox.
+*/
+
+progress {
+  vertical-align: baseline;
+}
+
+/*
+Correct the cursor style of increment and decrement buttons in Safari.
+*/
+
+::-webkit-inner-spin-button,
+::-webkit-outer-spin-button {
+  height: auto;
+}
+
+/*
+1. Correct the odd appearance in Chrome and Safari.
+2. Correct the outline style in Safari.
+*/
+
+[type='search'] {
+  -webkit-appearance: textfield;
+  /* 1 */
+  outline-offset: -2px;
+  /* 2 */
+}
+
+/*
+Remove the inner padding in Chrome and Safari on macOS.
+*/
+
+::-webkit-search-decoration {
+  -webkit-appearance: none;
+}
+
+/*
+1. Correct the inability to style clickable types in iOS and Safari.
+2. Change font properties to `inherit` in Safari.
+*/
+
+::-webkit-file-upload-button {
+  -webkit-appearance: button;
+  /* 1 */
+  font: inherit;
+  /* 2 */
+}
+
+/*
+Add the correct display in Chrome and Safari.
+*/
+
+summary {
+  display: list-item;
+}
+
+/*
+Removes the default spacing and border for appropriate elements.
+*/
+
+blockquote,
+dl,
+dd,
+h1,
+h2,
+h3,
+h4,
+h5,
+h6,
+hr,
+figure,
+p,
+pre {
+  margin: 0;
+}
+
+fieldset {
+  margin: 0;
+  padding: 0;
+}
+
+legend {
+  padding: 0;
+}
+
+ol,
+ul,
+menu {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+}
+
+/*
+Reset default styling for dialogs.
+*/
+
+dialog {
+  padding: 0;
+}
+
+/*
+Prevent resizing textareas horizontally by default.
+*/
+
+textarea {
+  resize: vertical;
+}
+
+/*
+1. Reset the default placeholder opacity in Firefox. (https://github.com/tailwindlabs/tailwindcss/issues/3300)
+2. Set the default placeholder color to the user's configured gray 400 color.
+*/
+
+input::-moz-placeholder, textarea::-moz-placeholder {
+  opacity: 1;
+  /* 1 */
+  color: #9ca3af;
+  /* 2 */
+}
+
+input::placeholder,
+textarea::placeholder {
+  opacity: 1;
+  /* 1 */
+  color: #9ca3af;
+  /* 2 */
+}
+
+/*
+Set the default cursor for buttons.
+*/
+
+button,
+[role="button"] {
+  cursor: pointer;
+}
+
+/*
+Make sure disabled buttons don't get the pointer cursor.
+*/
+
+:disabled {
+  cursor: default;
+}
+
+/*
+1. Make replaced elements `display: block` by default. (https://github.com/mozdevs/cssremedy/issues/14)
+2. Add `vertical-align: middle` to align replaced elements more sensibly by default. (https://github.com/jensimmons/cssremedy/issues/14#issuecomment-634934210)
+   This can trigger a poorly considered lint error in some tools but is included by design.
+*/
+
+img,
+svg,
+video,
+canvas,
+audio,
+iframe,
+embed,
+object {
+  display: block;
+  /* 1 */
+  vertical-align: middle;
+  /* 2 */
+}
+
+/*
+Constrain images and videos to the parent width and preserve their intrinsic aspect ratio. (https://github.com/mozdevs/cssremedy/issues/14)
+*/
+
+img,
+video {
+  max-width: 100%;
+  height: auto;
+}
+
+/* Make elements with the HTML hidden attribute stay hidden by default */
+
+[hidden] {
+  display: none;
+}
+
+*, ::before, ::after {
+  --tw-border-spacing-x: 0;
+  --tw-border-spacing-y: 0;
+  --tw-translate-x: 0;
+  --tw-translate-y: 0;
+  --tw-rotate: 0;
+  --tw-skew-x: 0;
+  --tw-skew-y: 0;
+  --tw-scale-x: 1;
+  --tw-scale-y: 1;
+  --tw-pan-x:  ;
+  --tw-pan-y:  ;
+  --tw-pinch-zoom:  ;
+  --tw-scroll-snap-strictness: proximity;
+  --tw-gradient-from-position:  ;
+  --tw-gradient-via-position:  ;
+  --tw-gradient-to-position:  ;
+  --tw-ordinal:  ;
+  --tw-slashed-zero:  ;
+  --tw-numeric-figure:  ;
+  --tw-numeric-spacing:  ;
+  --tw-numeric-fraction:  ;
+  --tw-ring-inset:  ;
+  --tw-ring-offset-width: 0px;
+  --tw-ring-offset-color: #fff;
+  --tw-ring-color: rgb(59 130 246 / 0.5);
+  --tw-ring-offset-shadow: 0 0 #0000;
+  --tw-ring-shadow: 0 0 #0000;
+  --tw-shadow: 0 0 #0000;
+  --tw-shadow-colored: 0 0 #0000;
+  --tw-blur:  ;
+  --tw-brightness:  ;
+  --tw-contrast:  ;
+  --tw-grayscale:  ;
+  --tw-hue-rotate:  ;
+  --tw-invert:  ;
+  --tw-saturate:  ;
+  --tw-sepia:  ;
+  --tw-drop-shadow:  ;
+  --tw-backdrop-blur:  ;
+  --tw-backdrop-brightness:  ;
+  --tw-backdrop-contrast:  ;
+  --tw-backdrop-grayscale:  ;
+  --tw-backdrop-hue-rotate:  ;
+  --tw-backdrop-invert:  ;
+  --tw-backdrop-opacity:  ;
+  --tw-backdrop-saturate:  ;
+  --tw-backdrop-sepia:  ;
+}
+
+::backdrop {
+  --tw-border-spacing-x: 0;
+  --tw-border-spacing-y: 0;
+  --tw-translate-x: 0;
+  --tw-translate-y: 0;
+  --tw-rotate: 0;
+  --tw-skew-x: 0;
+  --tw-skew-y: 0;
+  --tw-scale-x: 1;
+  --tw-scale-y: 1;
+  --tw-pan-x:  ;
+  --tw-pan-y:  ;
+  --tw-pinch-zoom:  ;
+  --tw-scroll-snap-strictness: proximity;
+  --tw-gradient-from-position:  ;
+  --tw-gradient-via-position:  ;
+  --tw-gradient-to-position:  ;
+  --tw-ordinal:  ;
+  --tw-slashed-zero:  ;
+  --tw-numeric-figure:  ;
+  --tw-numeric-spacing:  ;
+  --tw-numeric-fraction:  ;
+  --tw-ring-inset:  ;
+  --tw-ring-offset-width: 0px;
+  --tw-ring-offset-color: #fff;
+  --tw-ring-color: rgb(59 130 246 / 0.5);
+  --tw-ring-offset-shadow: 0 0 #0000;
+  --tw-ring-shadow: 0 0 #0000;
+  --tw-shadow: 0 0 #0000;
+  --tw-shadow-colored: 0 0 #0000;
+  --tw-blur:  ;
+  --tw-brightness:  ;
+  --tw-contrast:  ;
+  --tw-grayscale:  ;
+  --tw-hue-rotate:  ;
+  --tw-invert:  ;
+  --tw-saturate:  ;
+  --tw-sepia:  ;
+  --tw-drop-shadow:  ;
+  --tw-backdrop-blur:  ;
+  --tw-backdrop-brightness:  ;
+  --tw-backdrop-contrast:  ;
+  --tw-backdrop-grayscale:  ;
+  --tw-backdrop-hue-rotate:  ;
+  --tw-backdrop-invert:  ;
+  --tw-backdrop-opacity:  ;
+  --tw-backdrop-saturate:  ;
+  --tw-backdrop-sepia:  ;
+}
@@ -0,0 +1,8 @@
+window.remark_config = {
+    host: "https://remark42.avinal.space",
+    site_id: "remark",
+    show_rss_subscription: false,
+    theme: 'dark',
+    no_footer: true,
+};
+
@@ -0,0 +1,5 @@
+---
+date: "2023-01-01T08:00:00-07:00"
+draft: false
+title: Home
+---
@@ -0,0 +1,7 @@
+---
+date: "2023-01-01T08:30:00-07:00"
+draft: false
+title: Posts
+---
+
+All the posts.
@@ -1,14 +1,14 @@
 ---
-title: The Big Red Ants
-date: 2012-02-27 22:47
-tags: [ants, sav] 
 category: article
-description: 'The Big Red Ants'
-image: /images/ants.jpg
+date: 2012-02-27T22:47:00
+description: The Big Red Ants
+image: /images/ants.webp
+tags:
+- ants
+- sav
+title: The Big Red Ants
 ---

-# The Big Red Ants
-
 In a bird's eye view if we see around us, ants are the common and
 tiniest living entitiy seen by naked eye. One of them are the big red
 ants, in my view they are unique from others in two ways, first they
@@ -1,12 +1,18 @@
 ---
-title: प्रेम रतन धन पायो
-date: 2019-09-21 15:47
 category: article
-tags: [love, article, hindi]
+date: 2019-09-21T15:47:00
+description: प्रकृति की सुंदरता और कलाकारी हिमालय की कण-कण में झलकती है। प्रकृति ने
+  प्रेम को भी हिमालय के जितना ही विशाल और अलौकिक बनाया है । ये एक अलग चर्चा का विषय
+  है कि हिमालय पहले आया या प्रेम। मैं तो प्रेम के पक्ष में हूँ । वो हर अणु-परमाणु
+  जिन्होंने इतने बड़ा पहाड़ खड़ा किया वो सब आपस में प्रेम से बंधे हुए हैं।
+image: /images/fedora-night.webp
+tags:
+- love
+- article
+- hindi
+title: प्रेम रतन धन पायो
 ---

-# प्रेम रतन धन पायो
-
 टूटता तारा देखना एक अलौकिक अनुभव है। हिमाद्रि के छत से आसमान कुछ ज्यादा ही करीब प्रतीत होता है । लोग सदियों से हिमालय को पूजते आयें हैं ।
 दादा-दादी कहा करते थे ये जिंदा पहाड़ हैं । सारी बातें सुनते हैं लोगों की । उनके दुख दर्द दूर करते हैं, ये देवता हैं । आजकल जब रोज़ क्लास
 आते जाते दूर पहाड़ों की चोटियाँ देखता हूँ तो उनकी विशालता का अनुभव होता हैं । एक पल को अगर ये मान लिया जाए की हमारी सारी धार्मिक किताबें
@@ -0,0 +1,166 @@
+---
+category: article
+date: 2024-11-30T23:47:00
+description: Plant your lilies, and let them teach you how to grow.
+image: /images/soul-lily.webp
+tags:
+- Lily
+- Despair
+- Patience
+- Gardening
+- Plant
+- Heart
+title: How to grow Lilies?
+---
+
+Lilies, they say, are symbols of peace. But peace is not given; it is cultivated. Lilies demand
+effort, patience, and faith - a willingness to confront the barren soil and nurture it back to life.
+What follows is a guide to growing Lilies and a journey into a soul's quiet reckoning with despair.
+
+## What Once Was and Will be Again
+
+The garden was barren, its silence oppressive. The earth, dry and unyielding, clung stubbornly to
+its lifelessness as though it had forgotten how to nurture, how to hope. It stood as a monument to
+neglect, an expanse of quiet despair that seemed to whisper, Nothing will ever grow here again.
+
+And yet, something stirred - a faint whisper beneath the desolation, an inkling that even the most
+forsaken soil might still hold secrets of renewal. It was not certainty but a quiet rebellion
+against despair, a defiant act of belief. The decision to grow lilies was made not with confidence
+but with trembling hands, as if planting these flowers might coax life back into the hollow spaces
+of the heart.
+
+## From Ashes, We Rise
+
+To grow lilies, one must first break the earth. Not gently, but with purpose—plunging the spade into
+the hardened crust, forcing it to yield. Each strike dislodges fragments of the past: shards of what
+was once beautiful, tangled roots of pain buried so deep they have become part of the soil.
+
+The work is relentless. The ground resists, clutching its dead weight as though afraid of what might
+take its place. But with each motion, the soil begins to soften. The air fills with the earthy scent
+of transformation, a quiet promise that the past does not have to dictate the future.
+
+This is where the lilies begin—not with planting, but with clearing. The garden must first be
+emptied of its grief to make room for something new. It is an act of defiance and of hope, to
+believe that this barren soil can one day cradle life again.
+
+## Between a Rock and a Lily
+
+The bulbs are unremarkable, their appearance betraying nothing of what they might become. Holding
+them feels strange, as if they are too fragile to survive. And yet, there is a quiet power within
+them—a promise waiting to be fulfilled.
+
+Planting them is an act of faith and surrender, a quiet conversation between the gardener and the
+earth. Each bulb is placed with care, its position a deliberate choice. It is not enough to bury
+them; they must be cradled, surrounded by soil that is ready to nurture them.
+
+And then comes the waiting. Beneath the surface, where no eyes can see, the bulbs begin their secret
+work. It is a reminder that growth often begins in the darkness, in spaces where no light reaches.
+
+## Tend the Flame, Not the Ash
+
+The lilies require consistency. The soil must be tended to every day, watered with steady hands.
+Some days, the water feels heavy in your palms, as if the weight of the act might be too much to
+bear. But you do it anyway, knowing that without this care, the lilies cannot thrive.
+
+The sunlight is capricious. Some days, it floods the garden, bathing it in warmth. Other days, it
+hides behind thick clouds, forcing the lilies to stretch toward a light they cannot see. But they
+adapt. Lilies have a way of finding what they need, even in the absence of abundance.
+
+This daily ritual of watering and watching is its own form of prayer. Each drop of water, each
+fleeting moment of sunlight, whispers to the lilies: *Grow, even if it feels impossible. Grow, even
+when no one is watching.*
+
+## This Too Shall Bloom
+
+One day, the soil breaks open - not with a flourish, but with the quietest of gestures. A tiny green
+sprout emerges, barely noticeable, a sliver of life against the vastness of the earth.
+
+To the untrained eye, it is nothing. To you, it is everything. This fragile sprout is proof that
+something is happening beneath the surface, that your labor was not in vain. It is the first sign of
+life returning, the first whisper of hope finding its voice.
+
+But the sprout is not strong. It bends with the wind, threatened by the weight of even a single
+raindrop. Your instinct may be to shield it, to protect it from every possible harm. But lilies do
+not grow in safety. They grow in resilience.
+
+![Glimpse of the Lilies](/images/growing-lilies.jpg)
+
+## The Idea is Not to Abandon Ever...Never
+
+The garden is never free from trials. Storms roll in, their winds threatening to uproot what little
+has begun to grow. Pests arrive uninvited, gnawing at leaves and stems as though testing your
+resolve. The sun beats down mercilessly one day, only to disappear for weeks on end.
+
+It is in these moments that you are tempted to despair, to abandon the garden and declare it a
+failure. But lilies teach you that resilience is not about avoiding hardship; it is about enduring
+it. When the storm passes, you clear the debris. When pests arrive, you remove them. When the
+drought stretches on, you water the soil with your own tears if you must.
+
+Each act, no matter how small, is a promise to the lilies: *I will not abandon you*.
+
+## Bloom Where None Thought Possible
+
+And then, when you least expect it, the bloom arrives. It begins as a tightly closed bud, hesitant
+to reveal itself. Slowly, it unfurls, each petal a story of quiet perseverance. The bloom is
+breathtaking, not for its extravagance, but for its purity.
+
+Its beauty is unlike anything you imagined. It is not extravagant or loud, but it holds a quiet
+majesty. The petals, soft and delicate, seem to hum with a silent strength. This bloom is not just a
+flower—it is the culmination of every act of care, every moment of faith, every drop of water given
+when it felt like too much.
+
+The bloom reminds you that peace is not a permanent state but a transient gift. It must be cherished
+in its moment, for its impermanence is part of its beauty.
+
+## The Most Dangerous Thing About Me
+
+The most dangerous thing about me is that *I don't know how to give up*.
+
+When the storms tore through, I stayed. When the roots clung to the earth like they had a right to
+its emptiness, I dug deeper. Even when the soil screamed that nothing could ever grow here, I
+refused to listen.
+
+It's not resilience—it's defiance. A stubbornness that borders on recklessness. I don't know when to
+stop, even when the odds mock me. Even when it hurts.
+
+Maybe it's toxic. Maybe it's foolish. But here I am, hands in the dirt, refusing to abandon what
+could still bloom.
+
+## Faith Buried, Faith Unfurled
+
+To grow lilies is to embark on a journey of transformation. It is not about the flowers themselves
+but about what they symbolize—a return to life, a reclaiming of hope. The barren garden, once a
+place of despair, becomes a sanctuary.
+
+The lilies do not erase the struggles that came before them. The soil still bears the scars of its
+past, and the storms will come again. But the garden is no longer defined by its emptiness. It is
+defined by its capacity to grow.
+
+And so the lilies teach you their final lesson: Growth is not a destination but a process. It is a
+daily choice to clear the debris, plant the bulbs, and tend to the garden—even when it feels like
+nothing is happening. It is a faith that, with time and care, the lilies will bloom again.
+
+## This is not my Recipe
+
+I didn't write this. Or maybe I did. But I don't remember planting these thoughts. They feel
+foreign, like letters rearranged while I wasn't looking, like whispers heard through the hum of the
+wind.
+
+I think they've always been here, whispering just below the surface, tugging at my hands when I
+wasn't looking. They know things about me that I haven't told anyone. Things I've hidden. Things
+I've forgotten.
+
+Do you feel it too? The hum beneath the words, the tremor that isn't mine? It's as if the garden
+remembers something I don't. It isn't just soil. It's memory. It's pain. It's despair. It's rebirth.
+
+I wrote this, but I didn't write this. These aren't my words. But they're mine now, whether I wanted
+them or not.
+
+## Meet my Lilies
+
+And finally meet my most beautiful lilies. I have named them **Blood Demon Lily** and **Light Mode
+Lily**.
+
+![My Lilies](/images/my-lilies.jpg)
+
+Plant your lilies, and let them teach you how to grow.
@@ -0,0 +1,231 @@
+---
+category: blogs
+date: 2024-06-07T02:47:00
+description: In January, I started switching to terminal-based tools and just
+  recently, I was able to use my terminal for most of my development work.
+  This blog highlights what tools I am using and for what purposes.
+image: /images/dog-using-terminal.jpg
+tags:
+- terminal
+- zellij
+- neovim
+- tmux
+- zoxide
+- lazygit
+- fzf
+- atuin
+- alacritty
+- starship
+- toolbox
+- toolbx
+- gh
+- zsh
+- oh-my-zsh
+- cli
+- stow
+title: "Echoes from the Shell: The Tools That Talk Back"
+---
+
+I started programming on a Windows machine about 6 years ago. I had just joined
+college and had little clue about what tools to use and where to start. Slowly
+I learnt new things and knowing more tools from friends, seniors, blogs and
+YouTube. One thing was pretty common, almost everyone was recommending a Linux
+based OS. I wasn't completely ready to switch, so I started using WSL2. WSL2
+with Visual Studio Code were my daily driver for everything programming for
+next 2.5 years.
+
+## Linux loading
+
+I got selected into Google Summer of Code in 2021 and the project I was
+contributing to runs solely on Linux. So I finally left Windows and started
+using Ubuntu. I was also a part of GLUG (GNU/Linux Users Group) in my college,
+and that was one of the factors that motivated me to move. I used Ubuntu and
+VS Code for next 1 year.
+
+The next significant change to my setup came in 2022 January when I joined Red Hat
+as an Intern. And the first task given to me was "Remove everything on your
+ThinkPad and install Fedora". I used it for few months and then I switched to
+Fedora on my personal laptop as well. After using Fedora for 2.5 years now, I
+want to say Fedora is simply an excellent choice for students and developers
+alike (until you intend to use Arch and burn the world).
+
+## My current setup
+
+![Glimpse into the terminal](/images/terminal-workspace.png)
+
+*Note: Open the image in a new tab for better viewing.*
+
+Currently, I am using Fedora 40 with Sway Window Manager and tons of terminal
+based tools. Just to be clear, I am not a keyboard nerd, but it does get my
+work done faster and non-intrusively. I use a mouse for a fair share of my work
+(I own [Logitech MX Master 3s](https://avinal.space/posts/blogs/configuring-logitech-mouse-on-fedora/)).
+I will now be explaining what tools I use and why I prefer them. You can
+get additional information about them by simply an internet search as they are pretty
+famous.
+
+This is not a blog about replicating the exact setup. So I will omit the
+obvious tools, i.e. ZSH, plugins etc. Rather, I will enlist the major tools.
+I am going to divide my tools in few categories:
+
+- Tools I use for development
+- Enhancing Terminal capabilities
+- Miscellaneous
+
+## Tools I use for development
+
+This will be a trivial section, there are thousands of articles and videos
+on the internet that cover this topic. I am just going to add my two paise.
+
+### Neovim
+
+Well, I know. You are going to say "yeah, expected". But IIWII. I started using
+Neovim as my primary development tool in January this year. It was a little hard
+to get used to it, but once I got familiar it feels like a breeze. I switched
+from VS Code because of how bloated it is getting. I do not want a superfast
+editor with outstanding benchmarks and awesome features and customizability.
+Those are secondary, but most of all, I don't like being distracted. With all the
+new things getting into VS Code it felt like, just too many features than I
+need. I totally love VS Code, it was my daily drive for 5 years but
+I felt I needed something minimal, and minimal it is.
+
+I did some hopping from one config to another in the last 5 months and finally, I
+decided to configure it myself using kickstart repository and it works better
+than ever. I am still learning how to get most out of it.
+
+- [Neovim](https://neovim.io/)
+- [kickstart-modular.nvim](https://github.com/dam9000/kickstart-modular.nvim)
+- [Carbonfox from Nightfox.nvim theme](https://github.com/EdenEast/nightfox.nvim?tab=readme-ov-file#carbonfox)
+- [My configuration](https://github.com/avinal/dotfiles/tree/main/.config/nvim)
+
+### Lazygit
+
+When I moved from VS Code to Neovim, the one thing I missed most was a GUI
+git extension. Although I use git CLI for most of my VCS work, but having a
+visual display is helpful, especially for browsing changes and going through
+commit history. VS Code git extension is a great tool and lazygit almost
+replaces that for me. It has exactly those features that I generally use.
+Plus it is configurable, the default configuration is more than enough for
+most including me.
+
+- [Lazygit](https://github.com/jesseduffield/lazygit)
+
+### GitHub CLI
+
+Many people have mixed opinion about this tool. For me, it works best for
+what I generally do. And no, it doesn't replace git for me, I treat it like
+a snippet tool that does few things with minimal effort, which would otherwise
+take multiple commands using git. Additionally, most of the development work
+I do go to GitHub, so it helps with that as well.
+
+I mostly use it to clone, gist, creating pull requests, navigating issues,
+checking out pull request branches, creating new repositories, and sometimes
+for getting workflow status/logs. I strongly recommend it if you are eager to do
+more from your terminal.
+
+- [GitHub CLI](https://cli.github.com/)
+
+## Enhancing Terminal capabilities
+
+This category is focused on supercharging the default terminal with advanced
+capabilities like better prompt, multiplexing, configurable layouts, session
+management etc.
+
+### Alacritty
+
+What is wrong with Gnome terminal? Nothing. It is fantastic and I still use it
+for many tasks. When it comes to configuring your terminal and actually being
+able to reuse your configuration across machines, alacritty simply stands out.
+It has tons of configurations and I loved using it, so I switched to it.
+
+- [Alacritty](https://alacritty.org/)
+- [GitHub Monaspace Argon font](https://monaspace.githubnext.com/)
+- [My configuration](https://github.com/avinal/dotfiles/blob/main/.config/alacritty/alacritty.toml)
+
+### Zellij
+
+This one is interesting and new. I started using tmux as most people do when
+they want to increase the density of work in a single terminal. It works and
+is configurable as well. But there are some shortcomings for tmux. It does not
+let you save a layout and the session management is basic. If you restart, you
+will probably lose your setup.
+
+Zellij address these problems and includes many new features on top of it.
+You can create a layout in advance and also define what commands should be run
+on start. There is a native plugin system and you can write plugins in most
+languages that compile to WebAssembly. The configuration is human-friendly
+and you can have multiple configuration files.
+
+Initially, most users face issues with zellij default key bindings because of
+their conflicts with Neovim. I choose to use different leader keys for
+different tools. Here is the setup I use after getting recommendation on Reddit.
+
+- Neovim: Ctrl
+- Sway WM: OS Key/Command/Win Key
+- Zellij: Alt
+
+I also heavily modified the default key bindings as I saw fit. The tool is in
+active development with numerous features planned.
+
+- [Zellij](https://zellij.dev/)
+- [Zellij vs Tmux](https://github.com/zellij-org/zellij/discussions/1701#discussioncomment-3517152)
+- [My configuration](https://github.com/avinal/dotfiles/tree/main/.config/zellij)
+
+### Atuin
+
+I have covered Atuin before in my [last post](https://avinal.space/posts/raspi/everything-on-my-pi/#atuin).
+So this will be a brief mention here. Atuin helps you sync your command
+history across machines and provides excellent filtering and retrieval. If you
+need a backup of your command history, Atuin is a way to go.
+
+- [Atuin](https://atuin.sh/)
+- [My configuration](https://github.com/avinal/dotfiles/blob/main/.config/atuin/config.toml)
+
+## Miscellaneous
+
+This section focuses on the tools that aren't very common but they rather
+are unique in their own way, and you can get extra superpowers.
+
+### Toolbx
+
+This is more like a virtual terminal environment where you can install tools and
+packages without adding them to the host OS. For example, if you are testing
+some software, or want to build a project but don't want to install in your
+machine. Or even having multiple independent environment and multiple distros
+to develop your projects. I find this tool very useful. If you have such use
+cases, give it a try.
+
+- [Toolbx](https://containertoolbx.org/)
+
+### Fzf
+
+fzf is a companion tool that provides you fuzzy finding capabilities for a lot of
+common CLI tools. You can use it in a plethora of ways and the integration with
+tools are countless. It also comes with an interactive interface. This is a tool
+which I want to say, you will understand only when you use it.
+
+- [fzf](https://junegunn.github.io/fzf/)
+
+### zoxide
+
+zoxide brands itself as a smarter cd command, and this is precisely what it does.
+It remembers where you often go and helps you get there faster next time. It
+uses an impressive algorithm internally to rank the suggestions based on your
+use.
+
+- [zoxide](https://github.com/ajeetdsouza/zoxide)
+
+## Echos
+
+Here is the list of all other tools and plugins I didn't discuss, but they
+are a useful part of my daily work.
+
+- [Zsh](https://www.zsh.org/)
+- [Oh My Zsh](https://ohmyz.sh/)
+- [Starship](https://starship.rs/)
+- [telescope.nvim](https://github.com/nvim-telescope/telescope.nvim)
+- [mason.nvim](https://github.com/williamboman/mason.nvim)
+- [lazy.nvim](https://github.com/folke/lazy.nvim)
+- [GNU Stow](https://www.gnu.org/software/stow/)
+
+Please leave a comment, if you like reading this blog, or it helped you find a
+good tool.
@@ -0,0 +1,406 @@
+---
+title: Configure Logitech MX Master 3S using LogiOps
+date: 2023-09-25T20:47:00
+category: blogs
+tags: [fedora, mouse, "logid", "logitech", "logiops", "mx-master-3s"]
+image: "/images/mouse-building.webp"
+description: "I brought Logitech MX Master 3S mouse and it is a great mouse. It
+  has a lot of features and I am still exploring them. One of the features is to
+  configure the mouse using LogiOps. LogiOps is a command line tool to configure
+  Logitech devices on Linux distos."
+---
+
+I brought Logitech MX Master 3S mouse, and it is a great mouse. It has a lot of
+features, and I am still exploring them. One of the features is to configure the
+mouse using LogiOps. LogiOps is a command line tool to configure Logitech
+devices on Linux distros, since Logitech provides official tools to configure the
+mouse on Windows and macOS.
+
+## Logitech MX Master 3S
+
+Although I use keyboard shortcuts for most of my work, I still use the mouse a
+lot. It is usually very helpful to have a good mouse, especially when you have
+to scroll thousands of lines of code and documentation. This mouse features a
+superfast scroll wheel that can scroll thousands of lines in a second. In total
+there are 7 buttons on the mouse. The mouse can be connected to the computer via
+Bluetooth or a USB receiver. It can also be connected to multiple devices at the
+same time and can be switched between them using a button on the bottom of the
+mouse. The mouse can be charged using a USB-C cable, and it can be used while
+charging as well. You can see a 3D model of the mouse below. You can rotate the model using your
+mouse or touchpad.
+
+<iframe class="aspect-video w-full" title="Logitech MX Master 3 Mouse Black" frameborder="0" allowfullscreen
+  mozallowfullscreen="true" webkitallowfullscreen="true" allow="autoplay; fullscreen; xr-spatial-tracking"
+  xr-spatial-tracking execution-while-out-of-viewport execution-while-not-rendered web-share
+  src="https://sketchfab.com/models/c15eda7cd7874423a8c31d55193b9ff2/embed?ui_theme=dark&dnt=1"> </iframe>
+
+The best part about this mouse is that it is very comfortable to use and highly
+customizable. You can customize most of the buttons and even extend the functionality
+by adding gestures. You can also customize the scroll wheel and the scroll
+direction as well as the DPI and the pointer speed. All this can be done using
+LogiOps.
+
+## Installing LogiOps
+
+It is an open source tool with code available on [GitHub](https://github.com/PixlOne/logiops).
+This blog post will show you how to install and configure LogiOps on Fedora. The
+steps should be similar for other Linux distros and other Logitech mice as well.
+You can directly install using `dnf` but for latest version, you can build from
+source.
+
+- Install the dependencies.
+
+  ```bash
+  sudo dnf install cmake libevdev-devel systemd-devel libconfig-devel gcc-c++ glib2-devel
+  ```
+
+- Clone the repository.
+
+  ```bash
+  git clone https://github.com/PixlOne/logiops.git
+  ```
+
+- Build and install.
+
+  ```bash
+  cd logiops
+  mkdir build
+  cd build
+  cmake -DCMAKE_BUILD_TYPE=Release ..
+  make
+  sudo make install
+  ```
+
+## Configuring LogiOps
+
+In this blog post I will show you what buttons are available and how you can configure
+actions (*keypress* or *gestures*) on them. Let us take a look at all the available buttons.
+
+![Logitech MX Master 3S Buttons](/images/mx-master-3s-buttons.webp)
+
+You can also get a table of available buttons, their CID and available features
+by running logid in debug mode.
+
+```bash
+sudo logid -d
+```
+
+You can get output like this:
+
+```bash
+[INFO] Device found: MX Master 3S on /dev/hidraw4:255
+[DEBUG] /dev/hidraw4:255 remappable buttons:
+[DEBUG] CID  | reprog? | fn key? | mouse key? | gesture support?
+[DEBUG] 0x50 |         |         | YES        | 
+[DEBUG] 0x51 |         |         | YES        | 
+[DEBUG] 0x52 | YES     |         | YES        | YES
+[DEBUG] 0x53 | YES     |         | YES        | YES
+[DEBUG] 0x56 | YES     |         | YES        | YES
+[DEBUG] 0xc3 | YES     |         | YES        | YES
+[DEBUG] 0xc4 | YES     |         | YES        | YES
+[DEBUG] 0xd7 | YES     |         |            | YES
+[DEBUG] Thumb wheel detected (0x2150), capabilities:
+[DEBUG] timestamp | touch | proximity | single tap
+[DEBUG] YES       | YES   | YES       | YES       
+[DEBUG] Thumb wheel resolution: native (18), diverted (120)
+```
+
+You can see thumb wheel has some cool features like touch, proximity and single
+tap. Furthermore, you can configure these features in the configuration file. You can also
+configure the thumb wheel resolution.
+
+### Create a configuration file
+
+LogiOps uses a configuration file to configure the mouse. By default, the
+configuration file is located at `/etc/logid.cfg`. If you cannot
+find the file, you can create one. You can copy the default configuration file
+and edit it. You can find the default configuration file
+[here](https://github.com/PixlOne/logiops/blob/main/logid.example.cfg). You can
+read the documentation for the configuration file in [this wiki](https://github.com/PixlOne/logiops/wiki/Configuration).
+
+```bash
+sudo touch /etc/logid.cfg
+```
+
+You can also pass a custom path for the configuration file using `-c` flag. But
+it never worked for me, so I am going to skip this part.
+
+### Understanding the configuration options
+
+You can obviously read the documentation for the configuration file, but I will
+focus on easy understanding of the options that will be more than enough for most
+users. I will be building the configuration file step by step and finally show
+you the complete configuration file.
+
+- Add a device and define its name
+
+  ```cpp
+  devices: (
+    {
+      name: "MX Master 3S";
+    }
+  )
+  ```
+
+- Configure smartshift
+
+  ```cpp
+  smartshift:
+  {
+    on: true;
+    threshold: 30;
+    torque: 50;
+  }
+  ```
+
+- Configure hires scrolling
+
+  ```cpp
+  hiresscroll:
+  {
+    hires: true;
+    invert: false;
+    target: false;
+  }
+  ```
+
+- Configure dpi
+
+  ```cpp
+  dpi: 2000;
+  ```
+
+Next we will see how to configure the buttons.
+
+#### Buttons
+
+Every button has a CID. You can see the CID of the buttons in the debug output
+as well as in the image above. Every remappable button has some actions that can
+be configured. You can configure a keypress or a gesture or a combination of
+both.
+
+There can be two situations when you configure a button. Either you want to
+configure the button for a specific keypress, or you want to configure the button
+for a specific gesture. You can also configure the button for both keypress and
+gesture. In this case, the keypress will be triggered when you press the button
+and the gesture will be triggered when you press the button and move the mouse
+in a specific direction. The buttons can also be configured to toggle specific
+fetcures of the mouse like smartshift, hires scrolling, etc.
+
+First create a button section for the button you want to configure.
+
+```cpp
+buttons: (
+  {
+    <first-button>
+  },
+  {
+    <second-button>
+  }
+)
+```
+
+- Configure only a keypress, let's configure the wheel button to take screenshot
+
+  ```cpp
+  {
+    cid: 0x52;
+    action =
+    {
+      type: "keypress";
+      keys: ["KEY_PRINT"]
+    };
+  }
+  ```
+
+- Configure the top button to toggle SmartShift
+
+  ```cpp
+  {
+    cid: 0xc4;
+    action =
+    {
+      type: "ToggleSmartShift";
+    }
+  }
+  ```
+
+- configure the gesture button for the following (sway based gestures)
+  - keypress: Opens Terminal
+  - Up gesture: Snaps current window to top
+  - Down gesture: Snaps current window to bottom
+  - Left gesture: Snaps current window to left
+  - Right gesture: Snaps current window to right
+
+  ```cpp
+  {
+    cid: 0xc3;
+    action =
+    {
+      type: "Gestures";
+      gestures: (
+        {
+          direction: "Up";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_UP"];
+          };
+        },
+        {
+          direction: "Down";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_DOWN"];
+          };
+        },
+        {
+          direction: "Left";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_LEFT"];
+          };
+        },
+        {
+          direction: "Right";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys = ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_RIGHT"];
+          }
+        },
+        {
+          direction: "None"
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_ENTER"];
+          }
+        }
+      );
+    };
+  }
+  ```
+
+The keypress while using with gestures is defined as direction **None**. These are
+just some examples, you can go through the documentation to see all the available
+options.
+
+### Complete configuration file
+
+Here is the complete configuration file that I use.
+
+```cpp
+devices: (
+{
+  name: "MX Master 3S";
+  smartshift:
+  {
+    on: true;
+    threshold: 30;
+    torque: 50;
+  };
+  hiresscroll:
+  {
+    hires: true;
+    invert: false;
+    target: false;
+  };
+  dpi: 2000;
+
+  buttons: (
+  {
+    cid: 0xc3;
+    action =
+    {
+      type: "Gestures";
+      gestures: (
+        {
+          direction: "Up";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_UP"];
+          };
+        },
+        {
+          direction: "Down";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_DOWN"];
+          };
+        },
+        {
+          direction: "Left";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_LEFT"];
+          };
+        },
+        {
+          direction: "Right";
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys = ["KEY_LEFTMETA", "KEY_LEFTSHIFT", "KEY_RIGHT"];
+          }
+        },
+        {
+          direction: "None"
+          mode: "OnRelease";
+          action =
+          {
+            type: "Keypress";
+            keys: ["KEY_LEFTMETA", "KEY_ENTER"];
+          }
+        }
+      );
+    };
+  },
+  {
+    cid: 0x52;
+    action =
+    {
+      type: "Keypress";
+      keys: ["KEY_RIGHTCTRL", "KEY_PRINT"]
+    };
+  },
+  {
+    cid: 0xc4;
+    action =
+    {
+      type: "ToggleSmartshift";
+    };
+  }
+  );
+}
+);
+```
+
+## Post Configuration
+
+Once configured you will need to restart the logid service.
+
+```bash
+sudo systemctl restart logid
+```
+
+Voila! You have successfully configured your Logitech mouse.
+
+## References
+
+- [LogiOps](https://github.com/PixlOne/logiops)
+- [My Configurations](https://gist.github.com/avinal/2acfc0ac2952f4354dd3b4b78b8ccb2b)
@@ -0,0 +1,37 @@
+---
+title: Installing Fedora with automatic and custom partioning
+date: 2023-01-19 23:02
+category: blog
+tags: [fedora, partioning]
+image: ""
+draft: true
+---
+
+Fedora is one of the most popular Linux distribution for daily uses as well as
+development purpose. I have been a Linux user since 2019 and switched through
+multiple distros since then. For a long time I was stuck with Ubuntu and now
+finally Fedora. Fedora is an amazing distribution. You get to enjoy the latest
+of almost everything. But this all starts with installing Fedora on your system.
+Although Fedora is one of the most easy-to-install distribution out there, a lot
+of people struggle to install it the right way. There is a lot of tutorials and
+blogs as well, but I couldn't find one that answers all my questions and still is
+easy to understand and follow along. So I decided to write one.
+
+## What is the best for me?
+
+## Complete automatic installation
+
+## Semi-automatic custom partitioning
+
+## Advanced custom partitioning
+
+### Partition Scheme
+
+| Mount Points | Filesystem | Size (minimum) | Remarks |
+| --- | --- | --- | --- |
+| `/boot/efi` | EFI | | |
+| `/boot` | ext4 | | |
+| `/` | ext4 | | |
+| `/home` | btrfs | | |
+
+## References
@@ -0,0 +1,301 @@
+---
+category: blogs
+date: 2023-07-19T18:08:00
+description: In the last post, I described how to install Tekton Results on a Kubernetes
+  cluster. In this post, we will see how to use Tekton Results to store the results
+  of a PipelineRun and how to retrive them later.
+image: /images/tekton-results-retrieve.webp
+tags:
+- tekton
+- kubernetes
+- redhat
+- openshift
+- results
+title: Tekton Results - Storing and Retrieving Results
+---
+
+In the [last post](/posts/blogs/hey-tekton-results/), I described how to install
+Tekton Results on a Kubernetes cluster. In this post, we will see how to use Tekton
+Results to store the results of a PipelineRun and how to retrive them later.
+
+## Creating a PipelineRun/TaskRun
+
+Let us create a simple PipelineRun to see how Tekton Results works. Here is a simple
+PipelineRun that I created for this demo.
+
+- Create a PipelineRun YAML file.
+
+  ```sh
+  cat <<EOF > demo-pipeline-run.yaml
+  apiVersion: tekton.dev/v1beta1
+  kind: PipelineRun
+  metadata:
+    name: demo-pipeline-run
+  spec:
+    pipelineRef:
+      name: demo-pipeline
+      tasks:
+        - name: demo-task
+          taskSpec:
+            steps:
+              - name: demo-step
+                image: alpine
+                script: |
+                  echo "Hello World"
+  EOF
+  ```
+
+- Create the PipelineRun.
+
+  ```bash
+  kubectl apply --filename demo-pipeline-run.yaml
+  ```
+
+## Querying the Results API
+
+There are three ways to query the Results API. The simplest way is to use
+`tkn-results` CLI. You can also use `curl` or any other HTTP client as well as
+a gRPC client. I will go through all three methods. Before we start, we have to
+create a ServiceAccount and a ClusterRoleBinding to access the API.
+
+- Create a ServiceAccount for quering the API.
+
+  ```bash
+  kubectl create sa tekton-results-query -n tekton-pipelines
+  ```
+
+- Grant readonly permissions to the ServiceAccount
+
+  ```bash
+  kubectl create clusterrolebinding tekton-results-query \
+    --clusterrole=tekton-results-readonly
+    --serviceaccount=tekton-pipelines:tekton-results-query
+  ```
+
+- Create an access token
+
+  ```bash
+  export ACCESS_TOKEN=$(kubectl create token tekton-results-query -n tekton-pipelines)
+  ```
+
+- Expose the results API server, this will block so run in a separate shell.
+
+  ```bash
+  kubectl port-forward --namespace tekton-pipelines \
+    service/tekton-results-api-service 8080:8080
+  ```
+
+### Using `tkn-results` CLI
+
+We are not releasing the CLI yet, but you can install it using Go. You will need
+[Go](https://golang.org/doc/install) installed on your machine.
+
+- Install `tkn-results`
+
+  ```bash
+  GOBIN=${TKN_PLUGINS_DIR:-"${HOME}/.config/tkn/plugins"} \
+    go install github.com/tektoncd/results/tools/tkn-results@latest
+  ```
+
+- Query the API, pass `--insecure` flag if you are using a self-signed certificate. In place of `default` you can pass the namespace name. `-` means all namespaces.
+
+  ```bash
+  tkn-results list --insecure \
+    --addr http://localhost:8080
+    --authtoken $ACCESS_TOKEN
+    default
+  ```
+
+  You will get a response like below.
+
+  ```bash
+  Name                                                  Start                                   Update
+  default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be  2023-06-13 12:04:49 +0530 IST           2023-06-13 12:09:07 +0530 IST
+  ```
+
+- Similarly you can query Records for a particular PipelineRun or TaskRun Result.
+
+  ```bash
+  tkn-results records list --insecure \
+    --addr http://localhost:8080
+    --authtoken $ACCESS_TOKEN
+    default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be
+  ```
+
+  You will get a response like below. Notice that there are two records, one for the PipelineRun and one for the TaskRun.
+
+  ```bash
+  Name                                                                                               Type                                    Start                                   Update
+  default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be/records/dcb7926e-42e8-4338-ab7d-0b67e02389be  tekton.dev/v1beta1.PipelineRun          2023-06-13 12:04:51 +0530 IST           2023-06-13 12:19:09 +0530 IST
+  default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be/records/64a0ab6e-9b90-4e5e-a072-e44d8ff27467  tekton.dev/v1beta1.TaskRun              2023-06-13 12:06:14 +0530 IST           2023-06-13 12:07:52 +0530 IST
+  ```
+
+- Finally you can get a single record too.
+
+  ```bash
+  tkn-results records list --insecure \
+    --addr http://localhost:8080
+    --authtoken $ACCESS_TOKEN
+    default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be/records/dcb7926e-42e8-4338-ab7d-0b67e02389be
+  ```
+
+  You will get a response like below.
+
+  ```json
+  {
+  "name": "default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be/records/dcb7926e-42e8-4338-ab7d-0b67e02389be",
+  "id": "50b13d54-2eb0-4a45-8399-853f2d4ba028",
+  "uid": "50b13d54-2eb0-4a45-8399-853f2d4ba028",
+  "data": {
+    "type": "tekton.dev/v1beta1.PipelineRun",
+    "value": "eyJraW5kIjogIlBpcGVsaW5lUn<base64-encode-data-truncated-for-brevity>"
+    },
+  "etag": "50b13d54-2eb0-4a45-8399-853f2d4ba028-1686638949162394019",
+  "createdTime": "2023-06-13T06:34:51.320028Z",
+  "createTime": "2023-06-13T06:34:51.320028Z",
+  "updatedTime": "2023-06-13T06:49:09.162394Z",
+  "updateTime": "2023-06-13T06:49:09.162394Z"
+  }
+  ```
+
+### Using `curl`
+
+Using curl is similar to using `tkn-results` CLI. You can use the same access
+token and the same API server address. The only difference is that you have to
+pass the access token as a header and provide the API path depending on what
+you want to query.
+
+- Query the results
+
+  ```bash
+  curl --insecure \
+    -H "Authorization: Bearer $ACCESS_TOKEN"
+    -H "Accept: application/json"
+    https://localhost:8080/apis/results.tekton.dev/v1alpha2/parents/default/results
+  ```
+
+  You will get a response like below.
+
+  ```json
+  {
+  "results": [
+    {
+      "name": "default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be",
+      "id": "50b13d54-2eb0-4a45-8399-853f2d4ba028",
+      "uid": "50b13d54-2eb0-4a45-8399-853f2d4ba028",
+      "createdTime": "2023-03-02T07:26:48.972907Z",
+      "createTime": "2023-03-02T07:26:48.972907Z",
+      "updatedTime": "2023-03-02T07:26:54.191114Z",
+      "updateTime": "2023-03-02T07:26:54.191114Z",
+      "annotations": {},
+      "etag": "50b13d54-2eb0-4a45-8399-853f2d4ba028-1677742014191114634",
+      "summary": {
+        "record": "default/results/dcb7926e-42e8-4338-ab7d-0b67e02389be/records/dcb7926e-42e8-4338-ab7d-0b67e02389be",
+        "type": "tekton.dev/v1beta1.PipelineRun",
+        "startTime": null,
+        "endTime": "2023-03-02T07:26:54Z",
+        "status": "SUCCESS",
+        "annotations": {}
+      }
+    }
+  ],
+  "nextPageToken": ""
+  }
+  ```
+
+You can also use filters to query record for a particular (set of) PipelineRun
+or TaskRun. See the available filters [here](https://github.com/tektoncd/results/blob/main/docs/api/README.md#filtering).
+
+### Using gRPC
+
+You can also use gRPC to query the API. You can use the same access token. You
+will need to [install](https://github.com/grpc/grpc/blob/master/doc/command_line_tool.md)
+`grpc_cli` to query the API.
+
+- Querying using gRPC will need cert. Here is how to export them.
+
+  ```bash
+  kubectl get secrets tekton-results-tls -n tekton-pipelines \
+    --template='{{index .data "tls.crt"}}' | base64 -d > /tmp/results.crt
+  export GRPC_DEFAULT_SSL_ROOTS_FILE_PATH=/tmp/results.crt
+  ```
+
+- List available services
+
+  ```bash
+  grpc_cli ls --channel_creds_type=ssl \
+    --ssl_target=tekton-results-api-service.tekton-pipelines.svc.cluster.local \
+    localhost:8080
+  ```
+
+  You will get a response like below.
+
+  ```bash
+  grpc.health.v1.Health
+  grpc.reflection.v1alpha.ServerReflection
+  tekton.results.v1alpha2.Results
+  ```
+
+- List the Results
+
+  ```bash
+  grpc_cli call --channel_creds_type=ssl \
+    --ssl_target=tekton-results-api-service.tekton-pipelines.svc.cluster.local \
+    --call_creds=access_token=$ACCESS_TOKEN
+    localhost:8080
+    tekton.results.v1alpha2.Results.ListResults 'parent: "default"'
+  ```
+
+  You will get a response like below.
+
+  ```bash
+  connecting to localhost:8080
+
+  results {
+    name: "default/results/7afa9067-5001-4d93-b715-49854a770412"
+    id: "b74a3317-e6c0-421c-85d9-54b0f3d4b4c6"
+    created_time {
+      seconds: 1677742028
+      nanos: 143729000
+    }
+    etag: "b74a3317-e6c0-421c-85d9-54b0f3d4b4c6-1677742039224211588"
+    updated_time {
+      seconds: 1677742039
+      nanos: 224211000
+    }
+    uid: "b74a3317-e6c0-421c-85d9-54b0f3d4b4c6"
+    create_time {
+      seconds: 1677742028
+      nanos: 143729000
+    }
+    update_time {
+      seconds: 1677742039
+      nanos: 224211000
+    }
+    summary {
+      record: "default/results/7afa9067-5001-4d93-b715-49854a770412/records/7afa9067-5001-4d93-b715-49854a770412"
+      type: "tekton.dev/v1beta1.TaskRun"
+      end_time {
+        seconds: 1677742039
+      }
+      status: SUCCESS
+    }
+  }
+  ```
+
+Similar to curl you can pass filters here as well.
+
+## Conclusion
+
+In this post, we saw how to use Tekton Results to store the results of a PipelineRun
+or TaskRun and how to query them later. Tekton Results is still in alpha, we are
+working on adding more features to it. If you have any feedback or feature request,
+please feel free to open an issue [here](https://github.com/tektoncd/results/issues)
+or reach out to us on [Slack](https://tektoncd.slack.com/). Thanks for reading!
+
+## References
+
+- [Tekton Results](https://github.com/tektoncd/results)
+- [Tekton Pipelines](https://github.com/tektoncd/pipeline)
+- [Tekton Results API Specification](https://petstore.swagger.io/?url=https://raw.githubusercontent.com/tektoncd/results/v0.7.0/docs/api/openapi.yaml)
+- [Tekton Results CLI](https://github.com/tektoncd/results/tree/main/tools/tkn-results)
@@ -1,17 +1,18 @@
 ---
-title: Create the VLC User Documentation for one Mobile Port(Android)
-date: 2020-12-01 23:47
-modified: 2020-12-31 23:19
 category: development
-tags: [vlc, gsod, gsod2020]
-description: 'The project was to Create the VLC User Documentation for Android 
-Mobile Port which was previously hosted on VLC wiki pages. The major portion 
-of this was to start everything from scratch including chapter separation, 
-section organization.'
+date: 2020-12-01T23:47:00
+description: The project was to Create the VLC User Documentation for Android Mobile
+  Port which was previously hosted on VLC wiki pages. The major portion of this was
+  to start everything from scratch including chapter separation, section organization.
+image: /images/day-of-cone.webp
+modified: 2020-12-31 23:19
+tags:
+- vlc
+- gsod
+- gsod2020
+title: Create the VLC User Documentation for one Mobile Port(Android)
 ---

-# Create the VLC User Documentation for one Mobile Port(Android)
-
 VideoLAN is a non-profit organization that develops software for playing
 video and other media formats. VLC media player (commonly known as just
 VLC) is a free and Open Source cross-platform multimedia player and
@@ -273,3 +274,7 @@ thank every person at VLC and Google who were involved in this whole
 process. Thanks and Congrats to my fellow writer Abhishek Pratap Singh.
 This was a great opportunity to learn and meet awesome people. I learned
 a lot about Sphinx, reStructured Text and many other things.
+
+## ATTRIBUTION
+
+- [Image by Tom Bigelajzen](https://images.videolan.org/images/goodies/day-of-the-cones-ex2.jpg)
@@ -0,0 +1,172 @@
+---
+category: blogs
+date: 2023-03-16T20:47:00
+description: Tekton Results aims to help users logically group CI/CD workload history
+  and separate out long term result storage away from the Pipeline controller.
+image: /images/tekton-results-wall.webp
+tags:
+- tekton
+- kubernetes
+- redhat
+- openshift
+- results
+title: Tekton Results to the Rescue
+---
+
+What do you do with your Tekton Pipelines once it finishes? Depending on if it
+failed or passed, you may keep it to inspect the logs. For most of the users/organizations
+the simplest step is to keep the completed TaskRuns/PipelineRuns object on the
+cluster to retrieve the data later.
+
+Imagine having thousands of runs and although a single TaskRun object takes very
+small space compared to the scale of a production cluster, but these little
+things add up quickly, and soon your cluster will be burdened with objects that
+probably no one will ever revisit. The organization/user is keeping them
+just-in-case if they want to see the logs and other data later.
+
+Although in most of the cases there is a pruning policy that takes care of these
+objects. But there are multiple problems with this approach.
+
+- This type of storage is not reliable and very difficult to query.
+- If the scale is massive, this could lead to destabilization of the cluster.
+- If you have a pruning policy, the completed objects are cleaned, and you lose all the associated data as well.
+
+So, what is the solution, how can you save your pipelines' data without having to keep them on cluster?
+
+## Introducing Tekton Results
+
+As mentioned on the [project repository](https://github.com/tektoncd/results):
+
+> Tekton Results aims to help users logically group CI/CD workload history and
+> separate out long term result storage away from the Pipeline controller. This
+> allows you to:
+>
+> - Provide custom Result metadata about your CI/CD workflows not available in
+>   the Tekton TaskRun/PipelineRun CRDs (for example: post-run actions)
+> - Group related workloads together (e.g. bundle related TaskRuns and PipelineRuns into a single unit)
+> - Make long-term result history independent of the Pipeline CRD controller,
+>   letting you free up etcd resources for Run execution.
+
+In short, Tekton results archives the run data (called results) and logs to an
+external storage. Now you can safely prune completed TaskRuns/PipelineRuns and
+save run data and logs for a later visit. Let us see how actually Tekton Results
+works under the hood.
+
+### How Tekton Results Works?
+
+Tekton Results is composed of two main components.
+
+- A **watcher** to listen to creation/update of PipelineRuns or TaskRuns.
+- An **API Server** to query the persistent storage for data.
+
+In addition to that, Tekton Results needs a working database connection that can
+be a persistent storage on the same cluster or hosted externally such as RDS.
+If no external storage is attached, logs are also stored on a persistent storage
+on the cluster, you may use a S3 (or compatible) storage solution for that.
+
+The lifecycle of a _result_ is as below:
+
+1. The first step is to create a Tekton PipelineRun or TaskRun.
+2. The Watcher listens for any changes in the TaskRun or PipelineRun.
+3. On change, Watcher updates (or creates) a corresponding `Record` or `Result` using the Results API.
+   Watcher adds annotations to the TaskRuns or PipelineRuns with proper identifiers. Watcher uses
+   these annotations to decide if the `Result` has been created/updated/finished or not.
+4. You can now query the Results data using the API. If the run state is incomplete yet, the response
+   from the API will indicate that as well via the status flag.
+5. Once the TaskRun/PipelineRun has been completed, you can safely prune the resource object.
+
+## Installing Tekton Results
+
+Installing Tekton Results is easy. You can use Kubernetes or OpenShift cluster, for this particular
+demonstration, I will be using a Kind cluster and a local database.
+
+### Prerequisites
+
+- [Kind](https://kind.sigs.k8s.io/docs/user/quick-start/#installation) for a local Kubernetes cluster.
+- [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl)
+- [curl](https://curl.se/download.html) for querying the API.
+- [OpenSSL](https://www.openssl.org/source/) for generating certificates.
+
+### Let's start
+
+1. Create a Kind Cluster
+
+   ```bash
+   kind create cluster --name tekton-results
+   kind export kubeconfig --name tekton-results
+   ```
+
+2. [Tekton Pipelines](https://github.com/tektoncd/results) must be installed on
+   the cluster. You can install it using the command below.
+
+   ```bash
+   kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml
+   ```
+
+3. Generate a database root password and store as a Kubernetes Secret. If you are using an external
+   database, prove the credential for the same. Here is a bare minimum requirement as YAML.
+
+   ```yaml
+   apiVersion: v1
+   kind: Secret
+   metadata:
+     name: tekton-results-postgres
+     namespace: tekton-pipelines
+   type: Opaque
+   data:
+     POSTGRES_USER: postgres
+     POSTGRES_PASSWORD: <your-password>
+   ```
+
+   You can directly use the command line as well:
+
+   ```bash
+   kubectl create secret generic tekton-results-postgres \
+     --namespace="tekton-pipelines" \
+     --from-literal=POSTGRES_USER=postgres \
+     --from-literal=POSTGRES_PASSWORD=$(openssl rand -base64 20)
+   ```
+
+4. Generate a cert/key pair. You may use any cert management software to generate this. You can even
+   use cluster generated certs.
+
+   ```bash
+   openssl req -x509 \
+     -newkey rsa:4096 \
+     -keyout key.pem \
+     -out cert.pem \
+     -days 365 \
+     -nodes \
+     -subj "/CN=tekton-results-api-service.tekton-pipelines.svc.cluster.local" \
+     -addext "subjectAltName = DNS:tekton-results-api-service.tekton-pipelines.svc.cluster.local"
+   ```
+
+5. Create another TLS Kubernetes Secret with the name `tekon-results-tls` to store the cert/key pair.
+
+   ```bash
+   kubectl create secret tls -n tekton-pipelines tekton-results-tls \
+     --cert=cert.pem \
+     --key=key.pem
+   ```
+
+6. Install Tekton Results
+
+   ```bash
+   kubectl apply -f https://storage.googleapis.com/tekton-releases/results/latest/release.yaml
+   ```
+
+7. You can check the status of the deployments using the below command. Do not worry
+   if some deployments show `CrashLoopBackOff`. Wait for some time, and
+   they should all be running.
+
+   ```bash
+   kubectl get pods -n tekton-pipelines --watch
+   ```
+
+Once all deployments are ready, we can start creating some TaskRuns/PipelineRuns. In the next part
+of this blog, I will explain how to retrieve data from Tekton Results. Happy Reading.
+
+## References
+
+- [Tekton Results](https://github.com/tektoncd/results)
+- [Tekton Pipelines](https://github.com/tektoncd/pipeline)
@@ -1,14 +1,17 @@
 ---
+category: blogs
+date: 2021-01-04T21:47:00
+image: /images/hrt-singapore.webp
+tags:
+- HRT
+- hudsonrivertrading
+- interview
+- internship
 title: HRT (Hudson River Trading) Systems Internship Interview Experience
-date: 2021-01-04 21:47
-tags: [HRT, hudsonrivertrading, interview, internship]
-category: blog
 ---

-# `HRT (Hudson River Trading)` Systems Internship Interview Experience
-
 I applied for **Systems Internship - Summer 2021** back in December 2020
-at [Hudson River Trading](https://www.hudsonrivertrading.com) , New
+at [Hudson River Trading](https://www.hudsonrivertrading.com), New
 York. The internship description was: -

 > We are looking for highly motivated students who are eager to learn
@@ -0,0 +1,247 @@
+---
+category: blogs
+date: 2024-09-22T05:47:00
+description: Privacy is just like hope. It is the quintessential human delusion,
+  simultaneously the source of your greatest strength and your greatest weakness.
+  This post outlines my switch to GrapheneOS and my experiences so far.
+image: /images/grapheneos-kill-bloat.webp
+tags:
+- grapheneos
+- privacy
+- degoogle
+- android
+- pixel
+- google
+- security
+title: "GrapheneOS Saga: The Privacy-Centric Midlife Crisis"
+---
+
+In **The Matrix Resurrections**, Morpheus says *Not all seek to control. Just as not all wish to be
+free*. The ever-increasing cases of privacy invading technology and the number of people sprinting
+to adopting them reflects the quotes in its entirety. It is true that in the modern world it is
+nearly impossible to have control of your complete data. But with few changes, you can decide how
+much one has access to your data. Do remember once anything is on internet, it is forever.
+
+## My Smartphone Journey
+
+I got my first smartphone in 2014. It
+was [Samsung Galaxy Star Pro](https://www.gsmarena.com/samsung_galaxy_star_pro_s7260-5749.php), a
+very basic budget smartphone with Android 4.1. I used it until mid-2019, then for a few months I
+used ASUS ZenPhone Go. It belonged to my friend. This also means I have never used 3G on smartphone.
+It was a direct jump from 2G to 4G.
+
+My first good smartphone
+was [Nokia 6.1 Plus](https://www.gsmarena.com/nokia_6_1_plus_(nokia_x6)-9178.php). Excellent build
+quality, clean OS with decent performance. Camera quality was surprisingly excellent considering
+that it had almost no AI-based processing. Nokia can be a market leader in smartphone, but it seems
+either they don't care much or they aren't putting much effort. I had to leave this phone in a year
+because of severe charging port issue. Other than that it is still one of my most favourite
+smartphone.
+
+Then I bought [Google Pixel 4a](https://www.gsmarena.com/google_pixel_4a-10123.php) in January of
+2021. First gadget bought with my first earning. Pixel 4 and 5 series are my most favourite
+smartphones still. These are ergonomic and handy phones without many bells and whistles. The design
+is nice with good performance and clean OS. After these, things started going bad.
+
+My current smartphone is [Google Pixel 7a](https://www.gsmarena.com/google_pixel_7a-12170.php)
+bought in 2023. It is good, but for the price I would expect a little more. Takes excellent photos
+and the performance is decent. The stock OS is unfortunately not as clean as it used to be.
+
+## Why GrapheneOS?
+
+Before I can explain why I choose GrapheneOS, I should explain what I need. It can vary person to
+person and phone to phone. But the keywords are the same, privacy, security, performance and
+control.
+
+### What I Do Not Need on My Smartphone
+
+This is a very opinionated list of things I do not want on my phone. This is in part inspired by
+privacy and performance concerns. A lot of it comes from my way of interacting with smartphone.
+
+- AI: It is wonderful in quantities in which wine can be enjoyed. Too much of it and the phones
+  behaves exactly like a drunken, too much talk but very little of it makes any sense.
+- Apps I will never use: Every smartphone comes with some set of preinstalled applications. Some of
+  them as crucial for the phone to function normally. Some of them are useful but may have an
+  alternative. And others neither crucial nor useful. And on most phones you cannot even
+  uninstall/disable them. It makes no sense to keep two apps with same functions or apps with no
+  functions.
+- Spyware/Malware/Adware/Bloatware: On many smartphones these are intentionally installed. OK, maybe
+  not the first two, but definitely the next two. Most of the Chinese smartphones are riddled with
+  Adware and Bloatware, probably the reason why they are so cheap. They are privacy nightmares and
+  eat up your performance and battery.
+- Inability to control permissions: A smartphone is a huge data generator and gatherer. If wrong
+  entities have access to it, they may use it for nefarious purposes. One of the shocking example
+  is [How Facebook was able to track location using accelerometer](https://www.cpomagazine.com/data-privacy/facebooks-use-of-alternate-location-tracking-methods-to-circumvent-apple-privacy-protections-expands-to-accelerometer-data/).
+  So I would like to oversee what permissions each application has.
+- Gimmicks: IYKYK
+
+I still want my phone to be usable and have regular updates. I want it to perform close to what it
+was designed for.
+
+### It just makes sense
+
+Once you are clear that what you do not want on your smartphone, GrapheneOS immediately makes sense.
+I can achieve everything listed above and more. I actually researched and planned for almost a year
+before I finally installed it. Now that I have done it, I think there is no going back.
+
+## Installing using Fedora
+
+GrapheneOS can be installed using WebUSB or via command line. Both are simple, but WebUSB is
+simpler. Since Fedora is not in
+the [supported OS](https://grapheneos.org/install/web#prerequisites). WebUSB may not work, for me,
+it didn't. So I opened my favourite tool, the terminal and started
+typing. [Installation via CLI](https://grapheneos.org/install/cli) works flawlessly as long as you
+follow it step by step. There are few extra steps you might need for Fedora, that I will be
+explaining here:
+
+1. Install these packages:
+
+  ```bash
+  sudo dnf install android-tools
+  ```
+
+2. Follow the official instructions up
+   to [OEM unlocking and booting into bootloader](https://grapheneos.org/install/cli#booting-into-the-bootloader-interface)
+3. Check if fastboot can detect your device
+
+  ```bash
+  sudo fastboot devices
+  ```
+
+4. After that, you can continue following the instructions. Use `sudo`.
+
+Wait patiently, as it takes some time and there is not much interactive response. Be sure that the
+process has ended successfully before you disconnect your phone.
+
+## First Impressions
+
+The onboarding was short and clean. No account logins, no spooky agreements to accept. Once you set
+up your phone, it should feel like a minimal installation of any Linux distros, few necessaries
+preinstalled apps and nothing else.
+
+In GrapheneOS all apps are sandboxed, no matter what is its origin. They have similar permission
+scopes and no app is treated as royalty. On stock Android, some Google apps have system level
+access, which they absolutely don't need for function. Unlike most custom OS available, GrapheneOS
+is a completely de-Googled OS. You can see a detailed
+comparison [here](https://eylenburg.github.io/android_comparison.htm). This means you should be just
+fine without any Google Apps at all.
+
+## Getting It To Speed
+
+I wanted to retain my ease of use and most of previous apps. Some of them may be privacy invading
+but with newly gained superpowers, I should be able to control them. I do use a fair share of Google
+Apps as well as FOSS applications.
+
+![Fully Configured GrapheneOS - Lockscreen, HomeScreen and Apps Menu](/images/grapheneos-looks.webp)
+
+### My daily drivers
+
+These are everyday applications, like calendar, payment and banking apps, maps, messaging, phone,
+contacts, browser, email etc. To install apps from the Play Store, you will need to install Play
+Services first. This is easy, just go to the App Store and install them.
+
+### Enhancers
+
+There are few apps, mostly FOSS, that I use to improve my experience. In no particular order (its
+alphabetic):
+
+- [AdGuard Home Manager](https://github.com/JGeek00/adguard-home-manager): An AdGuard Home client
+  app, that lets me quickly control and manage my self-hosted AdGuard Home installation.
+- [Aegis](https://getaegis.app/): Probably the best 2FA apps that is also FOSS. Compared to popular
+  options like Google Authenticator, it encrypts your token at rest, lets you import and export as
+  well as take encrypted backups.
+- [Immich](https://immich.app/): A FOSS and self-hosted Google Photos replacement. Except editing,
+  it has everything you may need in a media backup app. Even more features are being added
+  regularly.
+- [Insular](https://secure-system.gitlab.io/Insular/): I use this to enable a separate work profile
+  where I keep all my less used or data hungry applications. When not in use, I can just pause them,
+  and it saves battery as well as enhances privacy.
+- [Lawnchair](https://lawnchair.app/): To be frank, I am unable to find a launcher that fits to my
+  liking. My favorite launcher is still the OP Nokia Lumia launcher. Lawnchair is a Pixel launcher
+  replacement with a lot more features and customizations. I use it
+  with [Arcticons](https://arcticons.com/).
+- [ServerBox](https://github.com/LollipopKit/flutter_server_box): I use this to keep an eye on my
+  servers and even make small updates via ssh.
+- [Tailscale](https://tailscale.com/): Three of the apps mentioned above will be unusable if not for
+  Tailscale. In layman terms, it is a p2p VPN that tricks all the participating devices like they
+  are connected in same local network. So you can access your remote servers and data without ever
+  exposing them to internet. Additionally, it also redirects your DNS request to a custom server (
+  like AdGuard Home) or even make one of your devices act as exit node.
+
+## Things I Loved
+
+New OS, new experiences and new things to love. There are many things that made me say _**Wow**_,
+but I will point out the most significant changes in my smartphone experience.
+
+### Game-changers
+
+- Google Pixels are known for churning out good performance out of comparatively less powerful
+  hardware. With recent AI outbreak, Google and other organizations are putting too much of it even
+  in places, that makes little sense. GrapheneOS is clean from all that bloat, not even the
+  Assistant. If I really need it, I can install specific applications.
+- Battery life improvement is the biggest visible change I observed. I am now getting around 25%
+  more screen time than before with similar uses.
+- I can now decide what permission each app has as well as stop their access to network completely
+  without relying on a third party app. You also get fine control for your location data as well as
+  activity indicator.
+- As I mention in my first point, Pixels have good performance, but GrapheneOS takes it to another
+  level. My phone feels significantly faster. This should be expected since you no longer have bloat
+  apps running in background.
+
+### Little things
+
+- You can archive any installed application instead of removing them. This makes sure that you don't
+  have to set up again but still get rid of them in practice.
+- Ability to install apps in user profiles without any App Store installation.
+- The usual things, you can see the complete list of improvements/new things
+  on [GrapheneOS features](https://grapheneos.org/features) page.
+
+## Things That Went Wrong
+
+Yes, not everything is great with GrapheneOS. There were some downsides, some failures as well loss
+of data. I backed up all my data before making the switch and still got a few things wrong.
+
+### Horribly Wrong :(
+
+- I lost my WhatsApp data completely. I am still a bit sad about it. This happened because WhatsApp
+  couldn't detect active backup on my Google Drive and decided to start new. This is a scary example
+  of how dependent everything is on Google, if WhatsApp had allowed independent backup, this would
+  not have happened. I did find a probable fix, but after I lost my data. You can use _Transfer
+  Chats_ feature of WhatsApp to transfer between phones. But you need two phones with latest
+  versions of WhatsApp, so not possible for me anyway. There was a lot of not-important data, few
+  important and some which I wanted to remove but couldn't. So the destiny decided it for me, it
+  seems.
+- GrapheneOS doesn't have a great backup solution. It uses an implementation of Seedvault, which is
+  secure but not reliable at all. Most of the time it simply doesn't work. Except USB backup,
+  nothing worked for me. That also means you have to regularly take manual backup.
+
+### Manageable
+
+- All banking apps worked, except PayTM. After some research, I found that it is not GrapheneOS
+  fault. It seems PayTM hardcoded application used for webview. The usual _Android System Webview_
+  is not available neither installable on GrapheneOS since it uses its own implementation. It is
+  okay, because I always use a different payment app.
+- Getting location to work was a little tricky. The first few attempts completely failed. GrapheneOS
+  uses something called _Reroute location request to OS_ which limits when and how Play Services can
+  access location. A great privacy feature, but it took some time to work.
+
+## Things I am missing
+
+- Reliable backups would be a major missing. The GrapheneOS seems to be working on it, but it may
+  take time.
+- Some of the features are not latest compared to Stock Android or even completely missing, i.e.
+  Wallpaper Chooser, Extreme Battery Saver, Digital Wellbeing, pausing of apps. I understand that
+  these may not be a priority for the team, so it's okay.
+- I loved _Now Playing_ feature on Pixel, it is not available.
+- Although GrapheneOS is extremely minimal, there are still apps you cannot remove. The preinstalled
+  apps for dialer, contacts and cameras are simple and do the work, but the UI is pretty outdated,
+  and they do not have many features. So I installed alternatives, but I cannot remove them. Some of
+  them can be disabled though.
+- There are few UI issues that need fixing. Not anything critical, but sometimes it bothers.
+
+## References
+
+- [GrapheneOS Website](https://grapheneos.org/)
+- [Comparison of Android ROMs](https://eylenburg.github.io/android_comparison.htm)
+- [Installation using Fedora - Forum](https://discuss.grapheneos.org/d/359-fedora-to-install-grapheneos/4)
+- [The Matrix Resurrections](https://www.imdb.com/title/tt10838180/)
@@ -0,0 +1,4 @@
+---
+title: Setup Remark42 from scratch on Oracle Cloud
+draft: true
+---
@@ -0,0 +1,312 @@
+---
+category: development
+date: 2021-05-24T23:56:00
+description: CMake stands for Cross-platform Make. Normally, a build tool like Make
+  will parse a configuration file (Makefile) that contains all the commands required
+  to build an artifact based on the source files and other resources inside the project.
+image: /images/cmake-office.webp
+slug: cmake-basics
+tags:
+- cmake
+- gsoc
+- fossology
+- gsoc21
+title: Hello CMake
+---
+
+CMake stands for Cross-platform Make. Normally, a build tool like Make
+will parse a configuration file (Makefile) that contains all the
+commands required to build an artifact based on the source files and
+other resources inside the project.
+
+I proposed a new architecture for FOSSology that uses CMake instead of
+bare-metal Make as a Google Summer of Code 2021 project. Although these
+tutorials will be useful for anyone interested in learning CMake they
+are specifically tailored to the FOSSology project. This is the first
+blog on CMake in this series. In this blog, I will discuss CMake syntax
+and various features.
+
+## What is CMake?
+
+![You CMake me happy:left](/images/cmake-happy.webp)
+
+CMake stands for Cross-platform Make. Normally, a build tool like Make
+will parse a configuration file (Makefile) that contains all the
+commands required to build an artifact based on the source files and
+other resources inside the project. On the other hand, CMake will also
+parse a configuration file (CMakeLists.txt), but instead of directly
+build the artifact, it’ll generate another configuration file that will
+build the artifact.
+
+This approach is very common in Computer Science and is called *adding
+another level of indirection*. In short, you may say that:
+
+With just one configuration file you’ll be able to generate different configuration files to build your project for different platforms (Make, Visual Studio, etc).
+
+Another nice CMake feature is the so-called out-of-source build. Any
+file required for the final build, executables included, will be stored
+in a separated build directory (usually called build/). This prevents
+cluttering up the source directory and makes it easy to start over
+again: just remove the build directory and you are done.
+
+## CMake Syntax
+
+![Compiling:right](https://imgs.xkcd.com/comics/compiling.png)
+
+CMake unlike Make is a configuration language itself. CMake supplies a
+rich library of inherent functions as well as common programming
+language features like conditions, looping, macros, and functions. In
+addition to that CMake is highly modular and you can always write a
+CMake module yourself independent of any project. Specifically for C/C++
+programming, it supplies commands to find and link libraries
+automatically and lot many features.
+
+### Language Rules
+
+As mentioned above CMake is a language itself hence there are some
+language rules related to syntax, comments, variables, etc.
+
+- There are two types of comment in CMake, both start with `#`
+    character. The first one is line comments, as clear by name it is
+    delimited by a newline. The other one is bracket comment and can
+    span until the matching brackets are found.
+
+    ```cmake
+    # This is a line comment and it ends with the line.
+
+    #[[This is a bracket comment and it can span up to multiple lines.
+    But it is only supported in CMake 3.0 or later.]]
+    ```
+
+- Variables in CMake are like any other programming language. They are
+    case-sensitive and have any alphanumeric characters. In general, it
+    is recommended using upper case names as variables. They can be
+    assigned and unassigned using `set` and `unset` commands. A variable
+    can be referenced using `${VARIABLE_NAME}`.
+
+    > CMake reserves some types of identifers:
+    >
+    > - begin with **CMAKE_**(upper-, lower-, or mixed-case)
+    > - begin with ***CMAKE***(upper-, lower-, or mixed-case)
+    > - begin with **_** followed by the name of any CMake Command
+
+- The CMake commands are case insensitive in the latest version (3.0)
+    of CMake. That means `message()`, `Message()` or `MESSAGE()` are all
+    same.
+
+### Basic CMake Commands
+
+- The `project()` command is used to set the name of the CMake project
+    and optionally a language that is used by the project. Every
+    top-level CMake configuration must have this option set. The syntax
+    is as below:
+
+    ```cmake
+    project (projectname [CXX] [C] [Java] [NONE])
+    ```
+
+    If no language is specified then CMake defaults to supporting C/C++.
+    If `NONE` is specified then no language support is enabled.
+
+- The `set()` command is used to set a variable to a value or lists of
+    values. It is one of the most used CMake commands. The accompanying
+    command is `unset()`. The `unset()` command is used to unset a
+    variable or remove a variable from the current scope. The syntax for
+    the three commands are:
+
+    ```cmake
+    set (BLOG_TITLE "CMake Introduction")                # assign single value
+    set (BLOG_TAGS "gsoc" "cmake" "fossology" "gsoc21")  # assign a list of values
+    
+    unset (BLOG_TITLE)                                   # unset BLOG_TITLE
+    ```
+
+- The `message()` command can be used to display formatted messages
+    with different alert modes. There are many
+    [modes](https://cmake.org/cmake/help/v3.20/command/message.html#general-messages)
+    of displaying messages. The syntax is :
+
+    ```cmake
+    message ([<mode>] "message text" ...)
+    
+    message(NOTICE "Hey this is ${BLOG_TITLE}")         # Example message with variable
+    ```
+
+- The `cmake_minimum_required()` is used to set the minimum CMake
+    version to use to generate the build files. If any older version is
+    used than specified then the user gets an error message. It must be
+    specified at the top of the *CMakeLists.txt* file.
+
+    ```cmake
+    cmake_minimum_required (VERSION 3.0)
+    ```
+
+- The commands `add_executable()` and `add_library()` specifies what
+    executables and libraries to build and what source files must be
+    used to build them. One of the two commands must be used for any
+    binary generation.
+
+    ```cmake
+    add_executable(<name> [WIN32] [MACOSX_BUNDLE] 
+        [EXCLUDE_FROM_ALL] 
+        [source1] [source2 ...])
+    
+    add_library(<name> [STATIC | SHARED | MODULE]
+        [EXCLUDE_FROM_ALL]
+        [<source>...])
+    ```
+
+### Flow Control
+
+CMake provides three flow control structures. They are conditional
+statements (`if`), looping constructs (`foreach` and `while`) and
+procedure definitions (`function` and `macro`). I will explain each of
+them one by one.
+
+- **Conditional Statements** The `if` command in CMake is just like
+    the `if` command in any other language. It evaluates its expression
+    and based on that either executes the code in its body or optionally
+    the code in the `else` clause.
+
+    ```cmake
+    if (FOO)
+        # do something here
+    elseif (BAR)
+        if (NESTED_BAR)
+            # do something nested here
+        endif(NESTED_BAR)
+        # do something else
+    else ()
+        # do something here
+    endif (FOO)
+    ```
+
+    You can use many operators to form complex conditions. Available
+    options are **NOT**, **AND**, **OR**, **COMMAND**, **DEFINED**,
+    **EXISTS**, **IS_DIRECTORY**, **IS_ABSOLUTE**, **MATCHES**,
+    **IS_NEWER_THAN**, and operators for numerical comparisons
+    **EQUAL**, **LESS**, **GREATER**, **STRLESS**, **STREQUAL**,
+    **STRGREATER**.
+
+- **Looping Constructs** The `foreach` command enables you to execute
+    a group of CMake commands repeatedly on the members of a list.The
+    first argument of the foreach command is the name of the variable
+    that will take on a different value with each iteration of the loop.
+    The remaining arguments are the list of values over which to loop.
+
+    ```cmake
+    foreach(<loop_var> <items>)
+        <commands>
+    endforeach()
+    ```
+
+    The `while` command provides for looping based on a test condition.
+    The format for the test expression in the `while` command is the
+    same as that for the `if` command described earlier.
+
+    ```cmake
+    while(<condition>)
+        <commands>
+    endwhile()
+    ```
+
+    It is worth mentioning that foreach loops can be nested and that the
+    loop variable is replaced prior to any other variable expansion.
+    This means that in the body of a foreach loop you can construct
+    variable names using the loop variable.
+
+- **Procedure Definitions** A function in CMake is very much like a
+    function in C or C++. You can pass arguments into it, and the
+    arguments passed in become variables within the function. The first
+    argument is the name of the function to define. All additional
+    arguments are formal parameters to the function.
+
+    ```cmake
+    function(<name> [<arg1> ...])
+        # write the function body here
+        <commands>
+    endfunction()
+    ```
+
+    Macros are defined and called in the same manner as functions. The
+    main differences are that a macro does not push and pop a new
+    variable scope, and the arguments to a macro are not treated as
+    variables but are string replaced prior to execution. This is very
+    much like the differences between a macro and a function in C or
+    C++. The first argument is the name of the macro to create. All
+    additional arguments are formal parameters to the macro.
+
+    ```cmake
+    macro(<name> [<arg1> ...])
+        # write macro definition here
+        <commands>
+    endmacro()
+    ```
+
+## A Hello CMake example
+
+This example compiles a simple *hello_cmake* program. This example and
+the terminal commands are used in Linux context, however there is very
+little difference in different platforms. Make sure to [install
+CMake](https://cmake.org/install/) for your platform.
+
+- Create a folder and create a file named `hello_cmake.cpp` in that.
+    You may add your own code. Here is my example code.
+
+    ```cpp
+    #include<iostream>
+    
+    int main() {
+        std::cout << "Hello CMake\n";
+        return 0;
+    }
+    ```
+
+- Create another file named `CMakeLists.txt` and add the following
+    script in that file.
+
+    ```cmake
+    cmake_minimum_required(VERSION 3.0)
+    
+    # set project name
+    project(hello_cmake)
+    
+    # print compiler info
+    message("The compiler is ${CMAKE_CXX_COMPILER}")
+    
+    # add executable
+    add_executable(Hello_cmake hello_cmake.cpp)
+    ```
+
+- Create another directory `build` and run the following commands.
+
+    ```bash
+    # create folder and change directory
+    mkdir build && cd build
+    
+    # run cmake config
+    cmake ..
+    
+    # build project
+    cmake --build .
+    ```
+
+You will be able to see a `Hello_cmake` binary in the *build* folder.
+Hooray you have successfully built a project using CMake. For more [read
+here](https://cmake.org/cmake/help/v3.20/guide/tutorial/index.html). In
+the next blog I will explain how to create CMake configuration for a
+more complex project.
+
+Thanks!
+
+## References and Credits
+
+- [CMake Website](https://cmake.org)
+- [CMake
+    Documentation](https://cmake.org/cmake/help/latest/index.html)
+- [Mastering CMake Book](https://www.kitware.com/what-we-offer/#books)
+- [CMake
+    Tutorial](https://cmake.org/cmake/help/v3.20/guide/tutorial/index.html)
+- [You (C)Make Me
+    Happy](https://prateekvjoshi.com/2014/02/01/cmake-vs-make/)
+- [Compiling xkcd.com](https://xkcd.com/303/)
@@ -1,11 +1,19 @@
 ---
-title: I am loving it! RedHat
-date: 2022-02-25 20:47
 category: development
-tags: [kubernetes, redhat, docker, golang, tekton, openshift, intern]
-description: I made it to the Red Hat as a DevTools intern. This post is about onboarding and how I prepared myself for working on the actual project.
+date: 2022-02-25T20:47:00
+description: I made it to the Red Hat as a DevTools intern. This post is about onboarding
+  and how I prepared myself for working on the actual project.
+image: /images/fedora-wall.webp
+tags:
+- kubernetes
+- redhat
+- docker
+- golang
+- tekton
+- openshift
+- intern
+title: My internship at Red Hat
 ---
-# My internship at Red Hat

 I have been contributing to open source for the last 3 years and Red Hat
 was one of the companies that I was very fond of. I must say all my
@@ -34,7 +42,7 @@ and many more.
 ## Learning on the Go

 There was a lot of learning and still a lot to learn. In a meeting with
-my manager Pradeepto Bhattacharya, I was told that I will be working on
+my manager [^1] Pradeepto Bhattacharya, I was told that I will be working on
 TektonCD or OpenShift Pipelines, and both of them require a sound
 knowledge of Golang, CI/CD, Containers, Docker, and Kubernetes. I was
 familiar with CI/CD, containers, and Docker but never used Golang and
@@ -74,7 +82,7 @@ end-to-end platform includes UIs, CLIs, APIs, and security that are
 engineered to work together across the entire application delivery
 lifecycle.

-![The Docker Architecture](/images/docker-architecture.png)
+![The Docker Architecture](/images/docker-architecture.webp)

 - [Docker and Containers -
  Katacoda](https://www.katacoda.com/courses/docker) *interactive
@@ -85,7 +93,7 @@ lifecycle.

 ### Kubernetes

-![Kubernetes tech](/images/kubernetes-architecture.png)
+![Kubernetes tech:left](/images/kubernetes-meme.webp)

 **Kubernetes** is the Greek word for a ship's captain. We get the words
 Cybernetic and Gubernatorial from it. The Kubernetes project focuses on
@@ -115,4 +123,7 @@ created and then transfer the request to Tekton API to create the
 corresponding resource on the OpenShift/Kubernetes cluster.*

 So are you interested in how it went? Please follow up with my [next
-blog](https://avinal.space/posts/development/lovely-dangerous-things-redhat.html).
+blog](https://avinal.space/posts/development/lovely-dangerous-things-redhat).
+
+[^1]: [MDN Web
+Docs](https://developer.mozilla.org/en-US/docs/Glossary/Developer_Tools)
@@ -1,14 +1,25 @@
 ---
-title: Developing Minimal Tekton Server
-date: 2022-02-27 20:47
-modified: 2022-03-07 22:47
 category: development
-tags: [tekton, go, kubernetes, openshift, redhat, intern, golang, openshift-pipelines]
-description: 'This blog is a descreptive account of the development of Minimal Tekton Server. This is highly technical in nature, so please make sure that you have sufficient knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my [previous blog]("https://avinal.space/posts/development/i-am-loving-it-redhat.html") to know about these topics.'
+date: 2022-02-27T20:47:00
+description: This blog is a descreptive account of the development of Minimal Tekton
+  Server. This is highly technical in nature, so please make sure that you have sufficient
+  knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my [previous
+  blog]("https://avinal.space/posts/development/i-am-loving-it-redhat.html") to know
+  about these topics.
+image: /images/development.webp
+modified: 2022-03-07 22:47
+tags:
+- tekton
+- go
+- kubernetes
+- openshift
+- redhat
+- intern
+- golang
+- openshift-pipelines
+title: Developing Minimal Tekton Server
 ---

-# Developing Minimal Tekton Server
-
 This blog is a descreptive account of the development of Minimal Tekton Server.
 This is highly technical in nature, so please make sure that you have sufficient
 knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my
@@ -37,14 +48,13 @@ to the final diagram. Yeah, we learned. I will be explaining our
 final(obviously) architectural diagram and try to make some sense out of
 band-aids and duct tapes.

-<img src="/images/mks-architecture.png"
-class="img-fluid my-3 img-fluid my-3" alt="The MKS Arhitecture" />
+![The MKS Architecture](/images/mks-architecture.webp)

 Let me start with explaining **What are MKS Resources?**. I hope you
 know at least tidbits about Kubernetes and by the definition: *A
 resource is an endpoint in the Kubernetes API that stores a collection
 of API objects of a certain kind; for example, the built-in
-:code:\`pods\` resource contains a collection of Pod objects.* But
+`pods` resource contains a collection of Pod objects.* But
 developers soon realized that these in-built resources were not enough
 for the ever-growing applications of Kubernetes. Here [custom
 resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
@@ -56,9 +66,7 @@ Definition](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/
 So MKS Resources are such custom resources that correspond to the
 TektonCD custom resources.

-<img src="/images/venus-flytrap.gif"
-class="float-md-right ml-3 float-md-right ml-3" width="250"
-alt="A venus flytrap engulphing an insect." />
+![A venus flytrap engulphing an insect.:right](/images/venus-flytrap.gif)

 Let us now focus on the box containing `Controller` and `API server`.
 The controller can be said as a stimulus-response mechanism. Take the
@@ -206,4 +214,7 @@ type SpaceTimeList struct {
 }
 ```

-### To be Continued
+### Attribution
+
+- Photo by [Luca Bravo](https://unsplash.com/@lucabravo?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/XJXWbfSo2f0?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText).
+  
@@ -1,16 +1,17 @@
 ---
-title: How I implemented WakaTime embeddable Coding Graph GHA?
-date: 2021-02-02 21:47
-tags: [wakatime, github-action, coding]
 category: development
-image: https://raw.githubusercontent.com/avinal/Profile-Readme-WakaTime/b281d074ee75f9626b39d10e2e518c6a297208a3/waka.png
-description: 'If you use WakaTime to track your coding activity. You can add that to 
-your README as a bar graph or embed it in your blog/portfolio. Just add this 
-action to any of your repositories and there you have it.'
+date: 2021-02-02T21:47:00
+description: If you use WakaTime to track your coding activity. You can add that to
+  your README as a bar graph or embed it in your blog/portfolio. Just add this action
+  to any of your repositories and there you have it.
+image: /images/waka.webp
+tags:
+- wakatime
+- github-action
+- coding
+title: How I implemented WakaTime embeddable Coding Graph GHA?
 ---

-# How I implemented WakaTime embeddable Coding Graph GHA?
-
 If you use WakaTime to track your coding activity. You can add that to
 your README as a bar graph or embed it in your blog/portfolio. Just add this
 action to any of your repositories and there you have it.
@@ -1,16 +1,17 @@
 ---
-title: Move WSL 2 Safely to another Drive
-date: 2020-12-31 19:07
-tags: [wsl, wsl2]
 category: development
-description: 'It is real pain when you have small SSD and Windows Subsystem for Linux
-(WSL) is growing exponentially in size. There is no easy way to move the
-WSL installation to another drive. Here in this blog I will discuss how
-to tackle this problem with bite size steps.'
+date: 2020-12-31T19:07:00
+description: It is real pain when you have small SSD and Windows Subsystem for Linux
+  (WSL) is growing exponentially in size. There is no easy way to move the WSL installation
+  to another drive. Here in this blog I will discuss how to tackle this problem with
+  bite size steps.
+image: /images/windows-wsl2.webp
+tags:
+- wsl
+- wsl2
+title: Move WSL 2 Safely to another Drive
 ---

-# Move WSL 2 Safely to another Drive
-
 It is real pain when you have small SSD and Windows Subsystem for Linux
 (WSL) is growing exponentially in size. There is no easy way to move the
 WSL installation to another drive. Here in this blog I will discuss how
@@ -21,13 +22,13 @@ use WinKey + X shortcut and select **Windows PowerShell(Admin)**.
 2. Check if the WSL 2 installation you are planning to move is is
 currently running/stopped.

-  ```powershell
-  PS C:\\Users\\Avinal> wsl -l -v
-  PS C:\\Users\\Avinal>
+```powershell
+PS C:\\Users\\Avinal> wsl -l -v
+PS C:\\Users\\Avinal>
  NAME      STATE           VERSION
-  * Ubuntu    Running         2
+* Ubuntu    Running         2
  Kali      Stopped         2
-  ```
+```

 3. If its running then you must stop the particular WSL distribution.
 (*Ubuntu* used as example)
@@ -89,3 +90,7 @@ PS C:\\Users\\Avinal> ubuntu config --default-user user_name

 10. Finally run `wsl` and you have successfully moved your WSL 2
    installation to another drive.
+
+## Attribution
+
+- [Image](https://www.atwix.com/magento/magento-2-with-docker-for-windows-and-wsl-2/)
@@ -1,11 +1,16 @@
 ---
-title: Google Summer of Code 2021
-date: 2021-08-19 23:07
-tags: [gsoc, FOSSology]
-category: development
-description: This is the final report of my Google Summer of Code 2021 at The FOSSology Project. 
+category: gsoc
+date: 2021-08-19T23:07:00
+description: This is the final report of my Google Summer of Code 2021 at The FOSSology
+  Project.
+image: /images/gsoc-wall.webp
+tags:
+- gsoc
+- FOSSology
+title: GSoC'21 Final Evaluation Report
 ---
-# Google Summer of Code 2021
+
+This is the final report of my Google Summer of Code 2021 at The FOSSology Project.

 <style>
 .rd {color:red;font-weight:bold}
@@ -30,16 +35,13 @@ via custom scripts.

 ## GitHub Actions CI/CD

-<img src="/images/ci.png"
-class="float-md-right rounded border border-info ml-3 float-md-right rounded border border-info ml-3"
-width="350" alt="A CI Meme" />
-
 Since the FOSSology project moved on Github, it has used only the free
 Travis CI service for OSS projects. At the time of writing Travis CI has
 reduced its free tier CI services. GitHub Actions provides faster
 builds. Since GitHub Actions is a fully managed service by GitHub, we
 don't need to know how to scale and operate the infrastructure to run
 it.
+![A CI Meme:left](/images/ci.webp)

 It is straightforward to use with GitHub because when we fork a
 repository, the actions automatically get forked. This allows you to
@@ -497,10 +499,6 @@ INCOMPLETE, <span class="or">ORANGE</span>: NOT NEEDED/DEPRECATED)

 ## How does it work and how to use it?

-<div class="embed-responsive embed-responsive-16by9">
-    <iframe class="embed-responsive-item" src="/images/second-build.webm" allowfullscreen></iframe>
-</div>
-
 The new build system retains the modular and hierarchical structure of
 the previous build system. On the other hand, the new build system
 provides several new flags to control the build. The new build system
@@ -724,7 +722,7 @@ Actions is almost complete and working as expected. But it is not free
 of drawbacks and issues. This section outlines the known issues at the
 time of writing.

-![A Bug Meme](https://imgs.xkcd.com/comics/conference_question.png)
+![A Bug Meme:right](https://imgs.xkcd.com/comics/conference_question.png)

 - Coverage builds may fail with linking errors.
 - Packaging prefix is the same as the install prefix. This requires the
@@ -0,0 +1,71 @@
+---
+category: gsoc
+date: 2021-07-14T12:29:00
+description: In the first phase of GSoC 2021 @ The FOSSology Project, I have completed
+  the desired milestone. As of now, FOSSology can be installed completely via CMake
+  and most of the components are working fine in initial testing.
+image: /images/tech-wallpaper.webp
+tags:
+- gsoc
+- FOSSology
+title: GSoC'21 First Evaluation Report
+---
+
+In the first phase of GSoC 2021 @ The FOSSology Project, I have
+completed the desired milestone. As of now, FOSSology can be installed
+completely via CMake and most of the components are working fine in
+initial testing.
+
+## Updates
+
+In the first phase of GSoC 2021 @ The FOSSology Project, I have
+completed the desired milestone. As of now, FOSSology can be installed
+completely via CMake and most of the components are working fine in
+initial testing.
+
+List of tasks completed
+
+- Added CMake build configurations for all the C/C++ agents for
+  executables, libraries, and coverages
+- Added CMake install configuration for all C/C++ and PHP agents as well
+  as extra components
+- Reworked the shell scripts and generated source files to make them
+  more compatible with CMake as well as better in terms of overall
+  compatibility with the latest tools.
+
+## Improvements
+
+- The new CMake build architecture is much more flexible to changes as
+  compared to hard-coded Makefiles.
+- CMake generated configurations support parallel build by default, this
+  has led to significant improvement in build time. CMake generated
+  configuration can now build the whole project within 2 mins or even
+  faster on more powerful CPUs (Both Ninja and Makefiles with the same
+  number of parallel processes) compared to 4-5 minutes previously.
+  *(These results are averaged from initial testing of new build
+  architecture)*
+- CMake supports out-source builds by default, which means the source
+  folders are not touched/modified while building, all build files and
+  residuals get their separate folder and the source tree can be cleaned
+  easily.
+- Developers can now opt for a long list of generators to build
+  FOSSology e.g Makefiles, Ninja as per their needs.
+
+## How to test
+
+Instructions to test the new Build system is in [this](https://github.com/avinal/fossology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now) wiki.
+
+## Known Issues
+
+- There may be a permission issue with some generated sources while
+  building. This can be bypassed for now by running
+  `sudo chmod +x <filename>` command.
+- Coverage builds may fail.
+
+## Postponed Tasks
+
+- configuration for tests are skipped for now
+
+## Work in Progress
+
+- Currently, I am working on packaging the FOSSology with CMake.
@@ -0,0 +1,49 @@
+---
+category: gsoc
+date: 2021-05-28T21:00:00
+description: This meeting is the first of the recurring weekly GSoC project meetings.
+  In this meeting the current status of progress according to the proposal was discussed
+  and some topics related to current build system based on Make and the new build
+  system based on CMake.
+image: /images/tech-wallpaper-1.webp
+tags:
+- gsoc
+- fossology
+title: Community Bonding Meeting 0
+---
+
+This meeting is the first of the recurring weekly GSoC project meetings. In this meeting the current status of progress according to the proposal was discussed and some topics related to current build system based on Make and the new build system based on CMake.
+
+## Discussions
+
+- **The current progress according to schedule**
+  - The blog on CMake is on the way.
+  - I have gone through the Makefiles to get a rough estimate of the
+    work.
+  - Published the GSoC project blog
+- **How are agents related to each other in terms of compilation?**
+  - Each agent is independently compiled and generally use the source
+    code in `lib` folder. If any agent needs other agent then it uses
+    the library files instead.
+- **Does every agent have a executable and library?**
+  - Not necessarily, there are agents written in C, C++ and PHP,
+    depending on what is the use the configuration can be different.
+
+## Conclusion and Further Plans
+
+- It would be better if I get started by creating CMake configuration
+  for any of the agent.
+- Fork and create a branch for development and mention the same in blog
+  or wiki.
+- Add a timeline section in blog or wiki as provided in the project
+  proposal.
+- Publish the CMake introductory blog.
+- Prepare a prototype/plan for next week.
+- Find out the best alternative for handling the global variables.
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Ayush Bhardwaj](https://github.com/hastagAB)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,41 @@
+---
+category: gsoc
+date: 2021-06-04T22:30:00
+description: In this second meeting points over default Makefiles were discussed.
+  Ninja can be used as an alternative for Makefiles.
+image: /images/tech-wallpaper-2.webp
+tags:
+- gsoc
+- fossology
+title: Community Bonding Meeting 1
+---
+
+In this second meeting points over default Makefiles were discussed. Ninja can be used as an alternative for Makefiles.
+
+## Discussions
+
+- **What is the use of** `Makefile.deps` **and** `Makefile.process`
+  **files?**
+  - `Makefile.deps` consists of many used and unused snippets. These
+    snippets help setup the build and test environment for fossology.
+    Since there are many directories that are hardcoded, special care is
+    required while replacing this file.
+  - `Makefile.process` generates a master variable from list of
+    variables. It assists the script in `Makefile.conf` file. These
+    files together generate a list of variables that can be used
+    throughout the build process.
+- The build can be made faster using **Ninja** instead of **Make**.
+- Ninja supports parallel builds by default.
+- Print the flags used once the CMake configuration is working. That
+  will help us debug the process.
+
+## Conclusion and Further Plans
+
+- Write a *CMakeLists.txt* for **lib**.
+- Push the working branch and update the link either on wiki or blog.
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,100 @@
+---
+category: gsoc
+date: 2021-08-06T22:47:00
+description: This week I worked on CMake testing configuration. Most of the time was
+  spent understanding the previous testing architecture.
+image: /images/tech-wallpaper-11.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 9 Meeting
+---
+
+This week I worked on CMake testing configuration. Most of the time was spent understanding the previous testing architecture.
+
+## Week 9 Progress
+
+> Initial CMake testing configuration added.
+>
+> - Few tests working, e.g copyright, nomos
+> - Improved packaging configurations
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **Is this a necessity that tests must be run as the fossy user?
+  Because when I run tests as me they as for permissions. But proceeds
+  as the fossy user.**
+
+  - No this is not required and this should not happen. They run under
+    fossy as they sometimes require writing into /srv/fossology. But if
+    they can run under other users that is an enhancement.
+
+- **I am getting a lot of install issues in C/C++ agent tests?**
+
+  ``` bash
+  Start 3: delagent_unit_test
+
+  3: Test command: /home/avinal/Documents/my_git/fossology/build/src/delagent/agent_tests/test_delagent
+  3: Test timeout computed to be: 10000000
+  3: install: cannot stat '/home/avinal/Documents/my_git/fossology/build/src/delagent/agent_tests/..//../../install/defconf/Db.conf': No such file or directory
+  3: install: cannot stat '/home/avinal/Documents/my_git/fossology/build/src/delagent/agent_tests/..//VERSION': No such file or directory
+  3: sh: 1: ../../../testing/db/createTestDB.php: not found
+  3: Failed to run ../../../testing/db/createTestDB.php -c /home/avinal/Documents/my_git/fossologbuild/src/delagent/agent_tests/testconf -e, exit code is:127 .
+  3/8 Test #3: delagent_unit_test ...............***Failed    0.02 sec
+  ```
+
+  - Not sure about the reason. I was suspecting Makefile but since they
+    are gone now, I think PHP files are calling some shell commands
+    causing this.
+
+- **Suggestions/Changes from Gaurav for fixing tests.**
+
+  - For clib-tests, it needs to be called from PHP file (via PHPUnit) as
+    it requires setting up a dummy repo. Check the
+    `src/lib/c/test/Makefile`
+  - For missing services.xml, the test cases include
+    `src/lib/php/common-container.php` which loads the file. It expects
+    it to be in current dir. Can be solved in two ways
+    - Create another common-container.php just for test cases with
+      correct paths.
+    - Edit the current file and take the help of environment variables.
+      For example, if a test variable is exported in env, find the XML
+      relative to it otherwise continue as normal and this variable can
+      be exported by CMake during the test.
+  - Scheduler tests do need `fossology_testconfig` from Makefile.deps
+    which set up the srv and create test configurations, DB, etc.
+    - Another shell script can be written to do all that and call it
+      from CMake. The PHP file called makes everything required in /tmp
+      so not an issue.
+    - The locations like `LOG_DIR, FOSSDB_CONF`, etc. in CMakeLists.txt
+      can be changed to some other values. I am guessing this is the
+      reason you were asked for the fossy password.
+  - File `src/copyright/agent_tests/Functional/cli_test.sh` needs to be
+    edited to take paths relative to build dir. It can also be made into
+    a .in file which is generated from CMake? So every path can easily
+    be updated.
+  - For PHP agents with missing version.php issue, there is a hack
+    possible
+    - Check
+      <https://www.php.net/manual/en/function.set-include-path.php>
+    - Another hack will be to use soft links for version.php in the
+      source.
+  - Other PHP issues like
+    `PHP Fatal error: Uncaught Error: Class 'Fossology\Lib\Agent\Agent' not found`
+    can only be solved by editing composer.json before doing composer
+    install (look for autoload: psr-4 ).
+  - For delagent, pkgagent, mimetype issues, something can be done here:
+    <https://github.com/avinal/fossology/blob/avinal/feat/testing/src/testing/db/c/libfodbreposysconf.c#L349>
+
+## Conclusion and Further Plans
+
+- Raise a pull request for all the progress till now.
+- Refactor the test source code according to suggestions.
+- Implement remaining testing configurations.
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,79 @@
+---
+category: gsoc
+date: 2021-08-14T22:47:00
+description: This week I implemented CMake testing configuration and fixed most of
+  the tests. As of now all but 5 tests are working fine.
+image: /images/tech-wallpaper-12.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 10 Meeting
+---
+
+This week I implemented CMake testing configuration and fixed most of the tests. As of now all but 5 tests are working fine.
+
+## Week 9 Progress
+
+> Testing configuration for all agents added
+>
+> - GitHub Actions Configuration added
+> - Fixed and refactored most of the tests
+> - Raised a pull request for all the works till now. [#2075](https://github.com/fossology/fossology/pull/2075)
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **I suspect that the Ojo regression test's expected data file is
+  outdated**
+  - Michael said that on their internal Jenkins CI, these tests are not
+    being run currently, so this might be possible that the file is
+    outdated.
+- **Since some of the tests need Makefile to install while testing,
+  CMake generated Makefiles and test Makefiles are conflicting, and
+  hence we are forced to use Ninja for testing. What can I do about
+  it?**
+  - Michael suggested using `--file=filename` flag with the make command
+    and change the name of the test Makefile to something else. This
+    will solve the problem.
+- **Mimetype is detecting executables as shared lib, is that expected or
+  needs to be fixed?**
+  - Mimetype internally depends on the *file* command to get the
+    mime-type. If the output of the *file* command is also the same then
+    it is okay.
+- **What is** `folderlist` **in
+  <https://github.com/fossology/fossology/blob/master/src/delagent/agent_tests/Functional/ft_cliDelagentTest.php#L126>
+  ?**
+  - `folderlist` is a view. Use `createViews()` function.
+- **Suggestions/Changes from Gaurav for fixing phpunit tests.**
+  - Please note the changes in `setUp()` function in
+    `src/lib/php/tests/test_common_license_file.php`
+  - The test database name is given to the constructor of TestPgDb and
+    can be anything as it gets deleted in `teardown()`
+  - The `dbmanager` is provided by the object, no need to initialize
+    global `PG_CONN` (it will be exposed by the library in case some of
+    the functions need it).
+  - All the tables needs to be explicitly mentioned to
+    `createPlainTables()` and their corresponding `createSequences()`
+    (you can get them using `\d tablename` from existing DB easily. Then
+    call the `alterTables()` to update the sequence. (I am not sure if
+    `createConstraints()` is required at all, try to remove)
+  - `tearDown()` is pretty easy, just need to call `fullDestruct()`. For
+    debugging, you can add `exit(-1);` after any line you as suspecting,
+    connect to DB and checkout the database, select/inspect tables.
+  - There is also `TestInstaller` class in case any of test case needs
+    the whole mods-enabled with fossology.conf, VERSION, etc. Please
+    check `src/cli/tests/test_fo_copyright_list.php` for quick
+    reference.
+
+## Conclusion and Further Plans
+
+- Fix the remaining tests.
+- Add week 8, 9 reports.
+- Add Final Evaluation Report.
+- Complete Final Evaluation.
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,91 @@
+---
+category: gsoc
+date: 2021-06-11T23:30:40
+description: In this third meeting, I demoed the working build system, currently building
+  executables and libraries, a lot of queries were resolved about writing version
+  files and attaching commits and hashes to the build.
+image: /images/tech-wallpaper-3.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 1 Meeting
+---
+
+In this third meeting, I demoed the working build system, currently building executables and libraries, a lot of queries were resolved about writing version files and attaching commits and hashes to the build.
+
+## Week 1 Progress
+
+> This week was mainly focused on analyzing the previous build system and framing a skeleton for the new build system.
+>
+> - Created the build configuration [analysis table](https://github.com/avinal/FOSSology/wiki/agents-spec#agents-configuration-list).
+> - Completed the basic skeleton.
+> - Completed the CMake configuration for libraries
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+> - Test on [GitPod](https://gitpod.io/#https://github.com/avinal/FOSSology/tree/avinal/feat/cmake-buildsystem) right inside your browser.
+
+## Discussions
+
+- **What are the flags needed for C and C++?**
+  - The `-g` flag enables debug.
+  - The `-O2` flag is used for optimizing.
+  - In FOSSology these two flags are used together by default for all
+    build purposes because it is desired to have an optimized binary but
+    some level of debugging information is also desired.
+- **The Makefiles have some compile-time preprocessor macro definitions
+  that need to be passed to each build.** The Makefiles have all the
+  path values passed as `'"..value.."'` format *(double quote inside
+  single quotes)*, however the commands produced by CMake have
+  `\"..value..\"` format *(escaped double quotes)*. Are they the same or
+  it needs to be changed?
+  - Currently, there is nothing to determine if they work the same or
+    not, but if the compiler would not have accepted them then, it would
+    have thrown an error. As long it is working these should be fine,
+    but will need to be checked in the final build.
+- **Are all libraries in FOSSology static?**
+  - No, by default no library is static. The format
+    `lib<library-name>.a` is confusing but no need to worry about it for
+    now, if this is working fine then no problem.
+  - In general, this format denotes a static library.
+- **How to add the version and commit information to the builds?**
+  - I have gone through [this
+    thread](https://cmake.org/pipermail/cmake/2018-October/068383.html)
+    on CMake's official mailing list. And they have suggested a lot of
+    options, but unable to decide which option to use. Gaurav said he
+    will see into this thread and for now, I should try writing a shell
+    script and test if that works.
+  - Same can be tested for the version too.
+- **What is** `_squareVisitor.h.pre` **used for?**
+  - They are used to generate source code at build time.
+- **Is there any inheritance structure in the build system?**
+  *(Michael)*
+  - For now, I am writing separate modules for the default operations
+    needed in most configurations. The final structure will be decided
+    in the final build.
+- **Where are all the binaries produced?** *(Gaurav)*
+  - They are located in the build folder with the same directory
+    structure as the original project.
+  - While installing the same will be used and none of the source
+    folders are ever disturbed.
+- **Are all flags taken from the Makefiles itself?** *(Anupam)*
+  - Yes and No, there are some flags that CMake uses by default, they
+    can be altered by changing the value for `CMAKE_C_FLAGS` and
+    `CMAKE_CXX_FLAGS`. One can also append their flags. Since not all
+    compilation requires all the flags, I have taken the default one
+    into cache variables, and others are appended while configuring for
+    a particular project.
+
+## Conclusion and Further Plans
+
+- Try the `monkbulk` in monk and `makefile.sa` in nomos.
+- Try adding the version and commit hash info.
+- Implement writing version files for each build.
+- Add proper comments in the `CMakeLists.txt` files.
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Ayush Bhardwaj](https://github.com/hastagAB)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,64 @@
+---
+category: gsoc
+date: 2021-06-18T23:30:00
+description: In this fourth meeting, a lot of questions were discussed related to
+  the existing build system and what things we have to drop or modify.
+image: /images/tech-wallpaper-4.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 2 Meeting
+---
+
+In this fourth meeting, a lot of questions were discussed related to the existing build system and what things we have to drop or modify.
+
+## Week 2 Progress
+
+> This week was mainly focused on creating CMake configuration for libraries, executables and coverage.
+>
+> - Added the configuration for libraries and executables
+> - Resolved parallel build problems with coverage configs
+> - Implemented generated source configurations
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **Should I generalize the coverage build for each agent?**
+  - Coverage depends on the agent_tests and may or may not be available
+    for all the agent. So follow the Makefiles and add the configuration
+    as it is in them.
+  - Leave coverage for them who don't have it already in their
+    Makefiles.
+- **What are :code:\`\$(AGENTLIB) \$(REPO) \$(DB)\` in the Makefiles?**
+  - They seems to be remains of previous build configuration. Until
+    there is a problem, ignore if you can not find the definitions.
+- **Can I refactor the directory structure of nomos and monk, it will
+  help keep the source code generation out of source directory?**
+  - Yeah, sure. As long as it does not affects the working of the
+    project you may refactor them to suit your needs.
+- **I am facing problems with due to headers included using angled
+  brackets, can I change them to double quotes instead?**
+  - Yeah that would be okay, anyway the general practice is to add user
+    header files using double quotes.
+- **Using -Werror flag in regexscan causes build to fail, should I
+  remove it?**
+  - Since `regexscan` is not the part of default build you can ignore
+    it.
+- **In scheduler source code the preprocessor macro value for
+  FOSSDB_CONF is different from that in lib, is that correct?**
+  - We have made some changes, please change it to the same as in lib.
+
+## Conclusion and Further Plans
+
+- Try adding the version and commit hash info.
+- Implement writing version files for each build.
+- Add proper comments in the `CMakeLists.txt` files.
+- Complete the coverage build configuration
+- Start implementing the install configurations
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,66 @@
+---
+category: gsoc
+date: 2021-06-22T23:22:00
+description: In this fifth meeting, question related to versioning and obtaining commit
+  hash were discussed, this was a short meeting.
+image: /images/tech-wallpaper-5.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 3 Meeting
+---
+
+In this fifth meeting, question related to versioning and obtaining commit hash were discussed, this was a short meeting.
+
+## Week 3 Progress
+
+> Version file Implementation
+>
+> - Initial functions on obtaining commit and branch info
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **What is the regex expression used for obtaining version
+  information?**
+  - The regex has recently been modified to cover recent versions. The
+    latest form is as below:
+
+    ``` cpp
+    ([[:digit:]]+.[[:digit:]]+.[[:digit:]]+)(-?rc[[:digit:]]+)?-?([[:digit:]]*)-?[[:alnum:]]*
+    ```
+
+  - You can also try alternatives to regex if possible for CMake.
+- **Should I use** `git describe --tags` **or**
+  `git describe --always HEAD` **for obtaining version information?**
+  - In FOSSology we always use `git describe --tags`, no exception
+    whatsoever.
+- CMake provides a preset configuration for the install path on GNU
+  systems, you can see the description
+  [here](https://cmake.org/cmake/help/v3.10/module/GNUInstallDirs.html)
+  based on the
+  [configuration](https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
+  suggested by the GNU After comparing the variables defined in
+  Makefile.conf with these, it seems directly taken from GNU standards.
+  So I wanted to ask if this would be okay to stick to the presets,
+  instead of manually declaring the same paths? The former step will
+  reduce the number of variables we are currently caching and will make
+  it flexible for different installation scenarios.
+  - Using the GNU standards is the ideal situation but FOSSology uses
+    slightly different locations. For example, all agents end up under
+    `/usr/local/share/fossology/` with their individual folders instead
+    of going to `/usr/local/bin/`.
+  - If the same results can be achieved by using the
+    `CMAKE_INSTALL_<dir>` and `CMAKE_INSTALL_PREFIX` then yeah, it will
+    be preferred.
+
+## Conclusion and Further Plans
+
+- Try adding the version and commit hash info.
+- Implement writing version files for each build.
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,83 @@
+---
+category: gsoc
+date: 2021-06-29T23:22:00
+description: In this seventh meeting question related to installing the FOSSology
+  were discussed.
+image: /images/tech-wallpaper-6.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 4 Meeting-1
+---
+
+In this seventh meeting question related to installing the FOSSology were discussed.
+
+## Week 4 Progress
+
+> CMake configuration files have been refactored to make each agent as a separate sub-project.
+>
+> - Symbolic links are installing.
+> - VERSION files can be generated now during configure step
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **There are two types of replacements CMake can configure file with.**
+  `@VARIABLE@` **and** `${VARIABLE}` **. Since in PHP** `$variable` **is
+  used, it may create problem for CMake replacements. So may I replace
+  them?**
+  - Yeah sure, go ahead. It will be more robust.
+  - The replacement of `$VARIABLE` can be stopped by using `@ONLY`
+    option in `configure_file(...)` command.
+- **How to generate vendor directory?**
+  - The code for generating vendor directory is in `src/Makefile`.
+  - Before executing code for the generation, make sure to copy
+    `composer.json` and `composer.lock` to the target directory.
+  - There is also a patch that FOSSology needs to function as intended.
+    Make sure to run that patch to check and apply.
+  - For now, we generate *vendor* while building, but it would be nice
+    if it can be generated in the build step.
+- **Currently I am generating the VERSION file in configure step itself.
+  Should I move it to the build or install step?**
+  - Yeah, please move it to the build step. As in configure step the
+    data might be outdated.
+- **Is there any configuration for Release that we can use to install or
+  test?** *(Michael)*
+  - Yeah, there are 4 inbuilt configurations for various levels of
+    optimization and can be applied to tests and installation.
+- **Is the VERSION file is generated for each agent or whole project at
+  once? Because in the latter case, the VERSION file can be generated as
+  the last step.**
+  - No agent has a VERSION file along with the main VERSION file for
+    FOSSology.
+- **How I can build and install a single agent or component?**
+  - There are two ways you can build and install a specific agent or
+    component only.
+
+  - The first one is quite simple. Just change your directory to the
+    specific agent's directory and run all the usual commands for
+    building and installing.
+
+  - The second one is a bit for typing work. This can be used directly
+    from the top-level directory. After configuring the CMake, you can
+    run the following command to install the specific component.
+
+    ``` bash
+    # for Unix Makefiles
+    make list_install_component # this will list all the available components
+    cmake -DCOMPONENT=<component-name> -P cmake_install.cmake
+    ```
+
+  - I am writing a macro that will let us install a component by simply
+    running `make install component`.
+
+## Conclusion and Further Plans
+
+- Implement generation of vendor directory.
+- Move VERSION file generation to build step.
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,59 @@
+---
+category: gsoc
+date: 2021-07-02T22:22:00
+description: In this eighth meeting questions related to post install generation were
+  asked. This was a short meeting.
+image: /images/tech-wallpaper-7.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 4 Meeting-2
+---
+
+In this eighth meeting questions related to post install generation were asked. This was a short meeting.  
+
+## Week 4 Progress
+
+> Version parsing logic implemented.
+>
+> - VERSION and COMMIT_HASH added to every executables.
+> - Installing part is complete except `cli`.
+> - Symbolic Links are installing and working fine.
+> - Version, Symbolic Links, `VERSION` file generation, `version.php` generation are now more modular and called via a single function for each agent
+> - Most dependencies are now moved to single configuration file.
+> - Vendor directory generation and installing are now working.
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **Why all the symbolic links in cli points to** `fo_wrapper`
+  **script?**
+  - The `fo_wrapper` script calls the PHP script on the symbolic link
+    that called the fo_wrapper. It also initializes any requirement
+    before calling the scripts.
+- **How to generate all the other configuration in**
+  `/usr/local/etc/fossology` **directory?**
+  - You can find the input files for all these configurations in the
+    `install/defcon` directory.
+- **What are** `OBSOLETEFILES` **in** `www/ui/Makefile` **?**
+  - They are kept for compatibility purposes. Although they have been
+    removed in the current versions of FOSSology, if a user installs a
+    new version on top of an older instance, then we should explicitly
+    remove those files.
+- **I have created a separate folder for generating vendor directory. Is
+  that okay?**
+  - Yeah, it should be fine, But it would be better to rename it to
+    something else. Or even better if moved to *www* itself. Since these
+    files are used by www.
+
+## Conclusion and Further Plans
+
+- Move `vendor` scripts to `www` directory.
+- Implement installing for FOSSology cli.
+- Implement installing configuration scripts.
+- Finish installation for testing
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,47 @@
+---
+category: gsoc
+date: 2021-07-09T22:22:00
+description: This week was dedicated to perfecting CMake Installation Configuration.
+  The installation was tested and bugs were discussed.
+image: /images/tech-wallpaper-8.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 5 Meeting
+---
+
+This week was dedicated to perfecting CMake Installation Configuration. The installation was tested and bugs were discussed.
+
+## Week 5 Progress
+
+> CMake Installation Configuration is almost complete.
+>
+> - FOSSology can be installed completely via CMake
+> - Post install script generation also added
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- There are permission problems while running bash script of `nomos`,
+  `monk` and `genvendor`.
+  - One possible fix can be to add `bash` before each bash scripts.
+  - The other fix is to modify shebang line in each script from
+    `#!/bin/sh` to `#!/bin/bash`.
+- In copyright agent same files are being compiled thrice, this is
+  slowing down the build.
+  - I am working on it. The problem is occurring because of three
+    different executables.
+  - I will try to combine the common objects together.
+- There are some redundant files in the installation. And VERSION file
+  is missing in `/usr/local/share/fossology`.
+
+## Conclusion and Further Plans
+
+- Fix copyright build.
+- Remove redundant files and folders.
+- Fix permission issues.
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,65 @@
+---
+category: gsoc
+date: 2021-07-23T22:22:00
+description: This week I implemented CMake packaging configuration for FOSSology.
+  There were two meetings in this week and this report covers both of them.
+image: /images/tech-wallpaper-9.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 7 Meeting
+---
+
+This week I implemented CMake packaging configuration for FOSSology. There were two meetings in this week and this report covers both of them.
+
+## Week 7 Progress
+
+> Initial CMake packaging configuration implemented.
+>
+> - Packages can be built according to the FOSSology previous packaging structure.
+> - Copyright, ecc and keyword now builds faster.
+> - To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **Where I can find packaging info for FOSSology?**
+  - All the scripts and companion files are located inside `debian`
+    folder.
+  - The most important files are `control`, which contains the
+    dependency and description of each package, and `rules` file, which
+    contains the make commands for creating the packages.
+- **What are** `${shlibs:Depends}` **and** `${misc:Depends}` ?
+  - They are dependencies required for creating Debian packages. CMake
+    should be adding them by default so we can safely ignore them.
+- **Will the new packages have the same structure as the old ones?**
+  *(Michael)*
+  - Yes for compatibility purposes Gaurav has suggested exactly follow
+    the same structure as the old one.
+- **Copyright build is slow because the same object files are being
+  compiled three times, can you improve that?** *(Gaurav)*
+  - I can try compiling the common object files beforehand and then
+    adding the executables. But how to know the common object files?
+  - Gaurav showed me where in the Makefiles I can find the common object
+    files.
+- There are problems with copying the symbolic link and packaging them.
+  So I have to find some alternatives to resolve that.
+- With component installing, package description can no longer be set.
+- The `fossology-common` package contains file from `fossology-db`
+  package. And the `fossology-db` package is empty.
+  - Gaurav said this was unexpected and should not happen. This seems to
+    be a very old bug with packaging.
+
+## Conclusion and Further Plans
+
+- Work more on the packaging.
+- Improve compilation of copyright and monk agents
+- Try to solve the packaging bug and add a pull request for that.
+- Move on to implementing testing configurations.
+
+## Attendees
+
+- [Michael C. Jaeger](https://github.com/mcjaeger)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Anupam Ghosh](https://github.com/ag4ums)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,59 @@
+---
+category: gsoc
+date: 2021-07-30T22:47:00
+description: This week I implemented CMake packaging configuration for FOSSology.
+  The new configuration fixes issue with previous packaging configurations. It also
+  retains the component wise installation features.
+image: /images/tech-wallpaper-10.webp
+tags:
+- gsoc
+- FOSSology
+title: Coding Week 8 Meeting
+---
+
+This week I implemented CMake packaging configuration for FOSSology. The new configuration fixes issue with previous packaging configurations. It also retains the component wise installation features.
+
+## Week 8 Progress
+
+> CMake Packaging configuration almost completed.
+
+- Packages can be built according to the FOSSology previous packaging structure.
+- Initial testing configuration added.
+- Ninja build has been fixed.
+- To test the current progress, follow the instructions [here](https://github.com/avinal/FOSSology/wiki#test-the-new-system-only-gcc-with-make-and-ninja-tested-for-now)
+
+## Discussions
+
+- **How is the testing implemented in FOSSology?**
+  - Not all agents have testing implemented.
+  - There are two types of tests *Unit* and *Functional*.
+  - At first, the test executable calls multiple PHP scripts to create a
+    test environment. And then tests are executed.
+  - Files related to testing and common for all the agents are in
+    `src/testing`
+  - Other tests depends on `phpunit`. This *PHPUnit* is generated inside
+    `vendor`.
+- **As of now, the testing configurations are hardcoded, what should I
+  do, because it seems the testing configuration will require changes to
+  a lot of files?**
+  - Decide a deadline for the testing configuration and if until that
+    point there is not very productive implementation then move to the
+    next task that is implementing CI.
+- As of now building, installation, and packaging via CMake is working
+  and in a stable state. To create an initial Pull Request. This would
+  also be useful in case of the final evaluation and further testing
+  will be based on this PR itself.
+- Fix any bugs or if there is the scope of improvement in Building,
+  Installation and Packaging do that.
+
+## Conclusion and Further Plans
+
+- Prepare for an initial PR.
+- Fix known bugs and apply Improvements.
+- Work on testing configurations.
+
+## Attendees
+
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Avinal Kumar](https://github.com/avinal)
@@ -0,0 +1,365 @@
+---
+category: gsoc
+date: 2023-03-30T21:14:00
+description: It has been 2 years since I was a Google Summer of Code Student. It was
+  an outstanding opportunity and I really enjoyed working on the project. Not only
+  that, but it added numerous skills to my resume and polished many others. Today
+  I want to make my proposal public, that helped me get selected.
+image: /images/panda-engineer.webp
+tags:
+- gsoc
+- fossology
+- proposal
+title: New Build System and improving CI/CD workflow
+---
+
+It has been 2 years since I was a Google Summer of Code Student. It was an outstanding opportunity and I really enjoyed working on the project. Not only that, but it added numerous skills to my resume and polished many others. Today I want to make my proposal public, that helped me get selected.
+
+## Current Build System and Workflow
+
+### Build System
+
+FOSSology’s build system is based on multilevel Makefile that work together to
+provide a build infrastructure for the project. Although make is a robust build
+system, but it is too outdated and slow compared to modern build systems. Although
+build configurations are not supposed to be updated as often as source files,
+there are few noticeable problems with make.
+
+* Configuration is mostly hard-coded, i.e., if needed to use different tools or add source files, the Makefile needs to be updated
+* All the dependencies and libraries have to be added manually by writing configuration for each of them
+* Although the FOSSology project currently supports Linux only, if in the future it has to be ported to other platforms, make won’t be able to support it. Hence, it is not future safe.
+
+### Workflow (Continuous Integration)
+
+FOSSology project has been using open-source tier Travis CI for all its continuous
+integration and deployment needs. GitHub launched its CI/CD system some years ago,
+and it has become a standard for CI/CD. Travis CI does the work but provides significantly
+fewer features when compared to GitHub Actions.
+
+* It has been observed that Travis CI is noticeably slower than GitHub Action for a similar configuration
+* Travis CI lacks the tight and seamless integration of GitHub Actions with other GitHub Services, some of them are the ability to integrate and communicate with GitHub apps, auto-manage to pull requests and issues, better support for Dockerized builds.
+
+## Why a New Build System(CMake)?
+
+There were many possible candidates for a new build system for the FOSSology project.
+Each has its pros and cons. After numerous comparisons and the ability of the new
+build system to integrate well with the existing system, CMake seems to be the best
+choice. Given below is a quick overview of different build systems and their execution times.
+
+![Configure and Build time comparision](/images/tools-build-comparision.webp)
+
+Here, CMake (Make & Ninja) performs better than average compared to other tools.
+The criteria for choosing CMake were not only performance, but many other factors.
+
+* The build system should be easily available on all supported distros - Cmake supports _UNIX, MS Windows (MSVC, Borland, Cygwin, MinGW) and Mac OS X, and more_
+* It should be easy to install – CMake is available via all popular package managers and repositories
+* Should improve build speed – In general, CMake always outperforms bare metal make systems.
+* The learning curve is not too steep – CMake is not very hard and neither too easy to learn. For common projects, it is easy to learn.
+
+### CMake Perks
+
+* No other dependencies apart from the C/C++ compiler
+* Includes a testing framework (CTest)
+* Includes a multipurpose packaging solution (CPack)
+* Migrating from Make to CMake is easier compared to other build systems
+* Can generate platform-specific build configuration; hence the same script can be used for multiple platforms
+* All modern C/C++ IDEs have inbuilt support for CMake or via a plugin (Visual Studio, XCode, CLion)
+* Can load dependencies automatically from the internet or local file system
+* Source and build folders are separate by default in CMake, this avoids bloating the source folders and accidentally deleting important files.
+
+### Comparison of CMake and Make syntax
+
+#### Make Syntax
+
+```makefile
+CXXFLAGS = -I../include -I.
+
+SRC := $(wildcard *.cc)
+DEP := $(patsubst %.cc,%.d,$(SRC))
+OBJ := $(patsubst %.cc,%.o,$(SRC))
+
+all: $(PROGNAME)
+
+$(PROGNAME): $(OBJ) ../lib/$(LIBNAME)
+    $(CXX) $(CXXFLAGS) $^ -o $@
+
+%.d: %.cc
+    $(CXX) -MM $(CXXFLAGS) $< | sed 's/\($*\)\.o[ :]*/\1.o $@ : /g' > $@
+
+ifneq ($(filter clean,$(MAKECMDGOALS)),clean)
+-include $(DEP)
+endif
+
+clean:
+    $(RM) $(DEP) $(OBJ) $(PROGNAME)
+```
+
+#### Corresponding CMake File
+
+```cmake
+include_directories(${CMAKE_CURRENT_SOURCE_DIR}/../include)
+include_directories(${CMAKE_CURRENT_SOURCE_DIR})
+
+AUX_SOURCE_DIRECTORY(${CMAKE_CURRENT_SOURCE_DIR} source)
+add_executable(hellocmake ${source})
+target_link_libraries(hellocmake LINK_PUBLIC libhellocmake)
+```
+
+### How to (c)make the move?
+
+#### Step 1: Determine the total number and types of Makefiles to migrate
+
+We will determine the required time for the whole migration and the number of respective
+CMake scripts to be written. In general, CMake scripts have fewer lines than Make
+scripts for the same task. However, the top-level CMake configuration can be very
+complex depending on how many configurations we want to create.
+
+* There are [168 Makefile](https://github.com/search?q=Makefile+repo%3Afossology%2Ffossology+filename%3A%22Makefile%22&type=Code)configurations as of now in FOSSology Project
+* Types: Build, Install, Test, Uninstall, Coverage, Clean, Package, and other sister types
+
+#### Step 2: Start migrating Makefiles one agent/directory at a time
+
+The FOSSology project’s build system follows a bottom-up approach. That means all
+the child directories need to be built first to build their parents. Since most
+of the agents in FOSSology are independent programs, their CMake config can be
+written separately. I have created a sample project to demonstrate the Make and
+CMake syntax and build process. It also demonstrates the cross-platform ability
+of CMake. The project can be accessed here: [https://github.com/avinal/make-cmake](https://github.com/avinal/make-cmake)
+
+#### Step 3: Create the Top-Level CMakeLists.txt to link all the libraries
+
+The top-level CMakelIsts.txt will be complex and most of the work, as well as testing,
+will be done during this phase. In the initial stage, I plan to create just the
+minimum to at least build the whole project in one go without any bells and whistles.
+
+#### Step 4: Add required configurations (Install, Package, Test)
+
+Once the top-level CMakeLists.txt is building the project without any problems.
+We will now add the required configurations such as install, package, test, uninstall,
+and other configurations.
+
+#### Step 5: Test the new Build System
+
+It is almost done, we may start testing our shiny build system. Checking every
+single configuration for errors and loopholes. This step will also make use of a
+new CI/CD system for testing purposes. Thus, simultaneously migrating the CI from
+Travis CI to GitHub Actions.
+
+## Improving the CI/CD workflow
+
+With the new build system, the FOSSology project will get a new CI/CD too. There
+were several tasks proposed for improving the workflow of FOSSology. I have completed
+many of them already. Given Below is an overview of the tasks proposed and their status.
+
+* Syntax Check ([#1919](https://github.com/fossology/fossology/pull/1919))
+* Static Code Analysis ([#1919](https://github.com/fossology/fossology/pull/1919))
+* Copy/Paste Detector ([#1919](https://github.com/fossology/fossology/pull/1919))
+* PHP Codesniffer ([#1919](https://github.com/fossology/fossology/pull/1919))
+* Docker Tests
+* C/C++ agent tests
+* PHPUnit tests
+* GitHub Page Release ([#1917](https://github.com/fossology/fossology/pull/1917))
+* Implementing Caching in workflows
+* Implement source install (reference[#207](https://github.com/fossology/fossology/issues/207))
+* DOC, Commit, and PR guideline checks
+
+### How will the workflow improve?
+
+We are migrating the whole workflow to the GitHub Actions platform, in general,
+GHA provides better integration and builds time.
+
+#### Step 6: Migrate the C/C++ agent tests and PHPUnit Tests
+
+By this time, we have already migrated our build system to CMake and thus the new
+workflow will be based on CMake configurations. The goal will be to add more platforms
+(Debian/Ubuntu/Fedora etc.) for tests and upgrade the tools to their latest compatible versions.
+
+#### Step 7: Implement Source Install test for Ubuntu, Debian, and Fedora
+
+As of now, source install is not tested for any of the distributions, so this step
+aims at adding source install testing capability to the new CI.
+
+#### Step 8: Implement caching in workflows and testing
+
+GitHub Action can store cache dependencies for a given period and thus reduces the
+number of times the virtual machine has to fetch packages. This in turn reduces
+the overall build time as well as reduces the load on servers.
+
+## Project Deliverables
+
+* New Build System (CMake) for the project
+* New Packaging, Install and Test configuration
+* C/C++ agents tests for multiple versions of GCC
+* PHPUnit tests
+* Docker Tests
+* Cached Workflows
+* Source installs tests for Debian, Ubuntu, Fedora
+* Checks for Pull Requests and Commit guidelines
+
+## Other Deliverables
+
+* For track my progress as well as a resource for future contributors, I will be writing a weekly/biweekly blog. The same can be used for preparing the final GSoC report.
+* Since CMake will be new for the FOSSology Community, I will document all the important topics that I will come across while migrating the build system. This will be both a handpicked resource and a reference for future contributors.
+* I would love to be a part of the community even after GSoC, although the build system and CI/CD doesn’t need to be updated that often, I would like to contribute to other parts of the project.
+
+## Experience
+
+I have 3 years of experience in C/C++ programming and one year of experience with
+CMake and Make. I have used CMake and Make for many of my projects, as well as contributed
+to other open-source projects. Furthermore, I have created/migrated the CI/CD for
+many open-source organizations to GitHub Actions, and created many personal projects
+using GHA as well.
+
+I have been contributing to many open-source organizations since 2019. I participated
+as a Technical Writer in the Google Season of Docs 2021 program under the VideoLAN
+organization. So, I have a nice understanding of open-source project workflow and
+contribution standards. I am well versed in Git and GitHub.
+
+## Tech Stack
+
+* CI/CD: **GitHub Actions, Travis CI**
+* Build Systems: **CMake, Make**
+* Languages: **C/C++, PHP, Shell Script**
+* Version Control: **Git, GitHub**
+* OS: **Ubuntu, Fedora, Debian**
+* Compilers: **GCC, Clang**
+* Containers: **Docker**
+
+## Proposed Timeline
+
+### Community Bonding (May 17th - June 6th, 2021)
+
+* Discussing and collaborating with fellow participants and getting familiar with the FOSSology community and projects.
+* Since CMake is new for our FOSSology community, I will learn and bring in the resources so that people get comfortable with it before the coding period starts.
+* Going through the codebase and plan strategies for the migration, his includes identification of various types, segregation of libraries, executables, and dependencies.
+
+### Coding Week 1 (June 7th - June 13th, 2021)
+
+* Plan the priority order of migration, and create lists for all different configurations
+* Create CMake configuration for libraries.
+* There are approximately 8 libraries, since configuration is not that complex, it should take no longer than 1 week to complete
+
+### Coding Week 2 & 3 (June 14th - June 27th, 2021)🚩
+
+* If libraries are complete, migrate the agents one by one, since FOSSOlogy is based on a modular architecture, many agents can be independently migrated
+* There are some 27 agents, 2 agents per day should take 2 weeks; hence I have merged these weeks.
+* Time may vary for different agents to be migrated to CMake, but on average, this should take 2 weeks.
+* Buffer Period
+
+### Coding Week 4 (June 28th - July 4th, 2021)
+
+* By now all the agents and libraries are migrated and presently the top-level CMakeLists.txt should be created. Since this file will be complex and will need all the child configuration to work, the testing and completion should approximately take 1 week.
+* This week will also check the overall gains in terms of performance and stability of the new build system.
+* This is also the minimum requirement for the build system to be said working and to add more configurations
+
+### Coding Week 5 (July 5th - July 11th, 2021)🚩
+
+* This week will continue the development of the Top-level CMake configuration.
+* More configuration will be added for Install, Test, Uninstall, Package
+* If completed, testing will start and will continue for the next week
+* Buffer Period
+
+### Coding Week 6 (July 12th - July 18th, 2021) First Evaluation
+
+* The build system is a very crucial element of the project; hence it must be tested thoroughly before final rolling.
+* This week, I will continue the development of all required configuration and testing of the new Build System.
+* By the end of this week, the new build system will be able to properly build the project and use the configurations, this also marks the end of the first phase and first evaluation.
+* Buffer Period
+
+### Coding Week 7 (July 19th - July 25th, 2021)
+
+* With all the build system working, this week will be used to migrate the CI from Travis to GitHub Actions starting with the C/C++ agent’s test
+* Now the C++ agent tests will be executed using the new Build System
+* If completed, then the PHPUnit test migration will start
+
+### Coding Week 8 (July 26th - August 1st, 2021)🚩
+
+* Complete the PHPUnit CI migration
+* Add Docker tests
+* Start implementing source install test CI
+
+### Coding Week 9 (August 2nd - August 8th, 2021)
+
+* Complete Source Install CI
+* Start implementing workflow caching
+* Fixing bugs and clearing backlogs
+* Buffer Period
+
+### Coding week 10 (August 9th - August 15th, 2021)🚩
+
+* Checking the build system
+* Checking the CI/CD
+* Completing reports and documentation
+* Update the existing documentation and readme for the new build system and CI
+
+### Final Evaluations (August 16th - August 23rd, 2021)
+
+* Code and report submission
+
+### Milestones 🚩
+
+1. All agents and libraries have now a CMake build configuration
+2. Top-level CMake configuration with a stable build
+3. Top-level CMake configuration with other configs i.e. install, package, test
+4. C/C++ agent tests, PHPUnit test implemented in CI
+5. CI/CD is complete according to the task list
+
+## **Pre GSoC Involvements**
+
+### In FOSSology
+
+* [feat(CI): Migrate API docs generation and deployment to GitHub Actions](https://github.com/fossology/fossology/pull/1917) [MERGED]
+* [feat(CI): Migrate Static Checks and Analysis to GitHub Actions from Travis CI](https://github.com/fossology/fossology/pull/1919) [MERGED]
+* [fix(make): Fix warnings in make for Ubuntu 20.04.2 LTS](https://github.com/fossology/fossology/pull/1923) [OPEN]
+* [Upgrade this project from PHP 7 to PHP 8](https://github.com/fossology/fossology/issues/1920) [ISSUE]
+* [Improving build system and CI/CD flow](https://github.com/fossology/fossology/discussions/1931) [DISCUSSION]
+
+### Other Contributions
+
+* [VideoLAN/VLC for Android User Documentation](https://code.videolan.org/docs/vlc-android-user) [PROJECT]
+* [boostorg/gil](https://github.com/boostorg/gil/issues?q=author%3Aavinal) [2 PR, 1 ISSUE]
+* [embox/embox](https://github.com/embox/embox/issues?q=author%3Aavinal) [1 PR]
+* [JetBrains/swot](https://github.com/JetBrains/swot/pulls?q=author%3Aavinal) [1 PR]
+* [jupyter-xeus/xeus-sqlite](https://github.com/jupyter-xeus/xeus-sqlite/issues?q=author%3Aavinal) [1 PR, 1 ISSUE]
+* [github/explore](https://github.com/github/explore/pulls?q=avinal) [2 PR]
+
+## My Development Environment
+
+* Operating Systems: Ubuntu 20.04 LTS, Windows 10 20H2
+* Editors: Visual Studio Code, Vim
+* IDE: Visual Studio, CLion
+* Internet Speed: 20 Mbps
+
+## References and Resources
+
+1. [A sample Make CMake project structure and comparison](https://github.com/avinal/make-cmake)
+2. [CMake Reference Documentation — CMake 3.20.0 Documentation](https://cmake.org/cmake/help/latest/)
+3. [A simple comparison](https://mesonbuild.com/Simple-comparison.html) of different build systems
+4. [Why the KDE project switched to CMake -- and how (continued)](https://lwn.net/Articles/188693/)
+5. [bksys / scons (Re: win32 port)](https://mail.kde.org/pipermail/kde-buildsystem/2006-January/000410.html)
+6. [CMake vs Make](https://prateekvjoshi.com/2014/02/01/cmake-vs-make/)
+
+## Motivation
+
+Ever since I came to know about GSoC(that was in my first year), I wanted to be
+a part of it. This was even before I got the idea of Open Source. Once I started
+contributing to open source, I started liking it and gradually became a part. I
+did Google Season of Docs 2020 under the VideoLAN organization and got a nice overview
+of open-source development, communities, and programs.
+
+I found that the FOSSology community is very passionate about open-source contributions,
+and they welcome experts and noobs alike. Other than that, open community meetings
+are one of the best things I encountered in my open-source journey. I hope by being
+a part of this community I will exchange skills and experiences and thus help both
+the community and me.
+
+## Commitments
+
+This summer, I don’t have any classes or internships. I found this project very
+fascinating, and I have already worked out a portion of this project, so this project
+is my _priority_. Although the program is supposed to be part-time, I will be able
+to work full time as well on weekends. I will attend all the meetings and prepare
+reports on time. I am an active member of the community presently, and will continue
+the streak during GSoC as well as after GSoC.
+
+**Thanks**
@@ -0,0 +1,3 @@
+---
+draft: true
+---
@@ -0,0 +1,142 @@
+---
+title: Everything on my Pi
+date: 2024-04-29T10:47:00
+category: raspi
+image: /images/big-raspberry-pi.webp
+description: A list of everything I have installed on my Raspberry Pi 5 and 4B.
+tags:
+
+- raspi
+- linux
+- pi
+- raspbian
+- debian
+- ubuntu
+- server
+- docker
+
+---
+
+I always wanted to have my self-hosted server when I was in college. Never had enough money to do much until recently.
+So after I got my first job, I have invested moderately (heavily ;)) in gadgets and stuff. And one of my most prized
+possession is my Raspberry Pi 4 and Raspberry Pi 5. I have been using it for a while now, and I have installed many
+useful things on both of them. So I thought I would share it with everyone. This is a list of everything I have on my
+Pi.
+
+## Hardware and Specifications
+
+- [Raspberry Pi 5 8GB Model](https://www.raspberrypi.com/products/raspberry-pi-5/)
+- [Raspberry Pi 4B 8GB Model](https://www.raspberrypi.org/products/raspberry-pi-4-model-b/)
+- [Raspberry Pi 15W USB-C Power Supply](https://www.raspberrypi.com/products/type-c-power-supply/)
+- [Raspberry Pi 27W USB-C Power Supply](https://www.raspberrypi.com/products/27w-power-supply/)
+- [Samsung SSD 970 EVO Plus 500GB](https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-970-evo-plus-nvme-m-2-500gb-mz-v7s500b-am/)
+- [WD Blue SA510 SATA SSD M.2 2280](https://www.westerndigital.com/en-in/products/internal-drives/wd-blue-sa510-sata-m-2-ssd?sku=WDS500G3B0B)
+- [Pimoroni NVMe Base for Raspberry Pi 5](https://shop.pimoroni.com/products/nvme-base?variant=41219587178579)
+- [PiBOX NVMe SSD Enclosure](https://pibox.in/product/nvme-m2-enclosure-pibox-india-nvme-ssd-enclosure-usb-3-2-10gbps-tool-free-m-2-nvme-case-pci-e-nvme-reader-usb-c-supports-m-bm-keys-2230-2242-2260-2280-ssds-powerful-jm583-chipset/)
+
+I already had a good quality ethernet cables and micro SD cards lying around. You may ask if I am using SSD then why use
+a SD Card. The simple answer is that I am using an SSD for storing everything, but all the OS functions are still run on
+the SD card. In an unlikely event, I can just pull out the SSD and plug it in a different machine to access my data.
+
+## Applications I am hosting
+
+I won't be going into many details about my configurations in this post. I will probably cover them in separate posts.
+Here I will put a list of all the applications I am hosting and what I use them for.
+
+I am using [Tailscale](https://tailscale.com/) to connect to my servers. They are locked down for access without
+Tailscale network. There is an open source alternative called [Headscale](https://github.com/juanfont/headscale) as
+well, but I haven't given much though of self-hosting them yet. For server management I am
+using [RunTipi](https://runtipi.io/). It uses docker compose to manage all application install.
+
+I will be listing the applications in the decreasing order of my priority.
+
+### Immich
+
+| Website                       | Source                                         | Category                 | Platforms         | Similar       |
+|-------------------------------|------------------------------------------------|--------------------------|-------------------|---------------|
+| [Immich](https://immich.app/) | [GitHub](https://github.com/immich-app/immich) | Photos and Videos Backup | Web, Android, iOS | Google Photos |
+
+Immich is the best open source and feature rich replacement to Google Photos. For starters the installation is very
+easy, and you can install clients on Android and iOS. You can also use a CLI import tool to upload all your media
+easily. You get most of the Google Photos feature expect the editing tools. The project is in active development and the
+feature set is increasing day-by-day. You can see a comparision with other FOSS
+alternatives [here](https://meichthys.github.io/foss_photo_libraries/).
+
+### Paisa
+
+| Website                     | Source                                            | Category                   | Platforms | Similar          |
+|-----------------------------|---------------------------------------------------|----------------------------|-----------|------------------|
+| [Paisa](https://paisa.fyi/) | [GitHub](https://github.com/ananthakumaran/paisa) | Finance and Budget Manager | Web       | Beancount,ledger |
+
+It is really hard to keep track of all expenses from multiple accounts and credit cards. There are great solutions and
+applications but either they are too [complex](https://www.firefly-iii.org/) or paid. If you still decide to use them
+most of them don't fit well with Indian users, simply because they were not planned with such users in mind. Nothing
+wrong there but mindset and habits of users matters a lot in such kind of applications. This application became my
+immediate favorite once I installed. There are many thing this application gets right. First of them is the ease to
+use UI and use of India specific terms and inspired from Indian spending habits. There is a bit of learning curve since
+this application builds on top of [Plain Text Accouting](https://plaintextaccounting.org/), but it starts making sense
+once you learn it. The developer is an experienced Software engineer from India. This will work for most of the world
+but for Indian users this is a must-have if you are looking for such application. I wish it can have an android app as
+well. But the current web UI is more than enough.
+
+### Vikunja
+
+| Website                        | Source                                        | Category     | Platforms | Similar               |
+|--------------------------------|-----------------------------------------------|--------------|-----------|-----------------------|
+| [Vikunja](https://vikunja.io/) | [Gitea](https://kolaente.dev/vikunja/vikunja) | Todo, Kanban | Web       | Google Tasks, Todoist |
+
+There are many great open source todo and kanban applications, I have tested many of them and settled for Vikunja. For
+personal use it was easy to set up. It has all the necessary features but is not bloated. The UI is good and it also
+supports CalDAV. An Android application is still in progress but you can utilize CardDAV with applications
+like [DavX5](https://www.davx5.com/) or [Tasks.org](https://tasks.org/). You can also create teams and have
+different projects.
+
+### Atuin
+
+| Website                    | Source                                     | Category           | Platforms             | Similar    |
+|----------------------------|--------------------------------------------|--------------------|-----------------------|------------|
+| [Atuin](https://atuin.sh/) | [GitHub](https://github.com/atuinsh/atuin) | Shell History sync | Linux, MacOS, Android | zsh-histdb |
+
+I have 4 servers and many devices, it is not often easy to get the similar commands on different machines. That is where
+Atuin comes in. Atuin replaces your existing shell history with a SQLite database, and records additional context for
+your commands. Additionally, it provides optional and fully encrypted synchronisation of your history between machines,
+via an Atuin server.
+
+### Gitea
+
+| Website                           | Source                                      | Category         | Platforms | Similar                   |
+|-----------------------------------|---------------------------------------------|------------------|-----------|---------------------------|
+| [Gitea](https://about.gitea.com/) | [GitHub](https://github.com/go-gitea/gitea) | Git hosting, VCS | Web       | GitHub, BitBucket, GitLab |
+
+Gitea is a GitHub replacement written in Go. It includes a lot of features from GitHub including package registry,
+CI/CD, team collaboration etc. I have not been actively using it. But I plan to host my personal projects here.
+
+### Paperless-ngx
+
+| Website                                          | Source                                                   | Category                   | Platforms    | Similar  |
+|--------------------------------------------------|----------------------------------------------------------|----------------------------|--------------|----------|
+| [Paperless-ngx](https://docs.paperless-ngx.com/) | [GitHub](https://github.com/paperless-ngx/paperless-ngx) | Document Management System | Web, Android | Docspell |
+
+This is a document management application where I can store my PDF/text documents (not ebooks). It has built in OCR and
+other useful feature to organise and search through your documents.
+
+### Shiori
+
+| Website | Source                                        | Category         | Platforms                  | Similar            |
+|---------|-----------------------------------------------|------------------|----------------------------|--------------------|
+| -       | [GitHub](https://github.com/go-shiori/shiori) | Bookmark Manager | Web, Linux, MacOS, Windows | LinkWarden, Pocket |
+
+Shiori is a simple bookmarks manager written in the Go language. Intended as a simple clone of Pocket. You can use it as
+a command line application or as a web application. This application is distributed as a single binary, which means it
+can be installed and used easily. There is a third party Android app as well. You can get
+it [here](https://f-droid.org/en/packages/com.desarrollodroide.pagekeeper/).
+
+## What is missing
+
+I am still searching apps for a general purpose file server and ebook management. A lot of people have suggested and I
+have also tried Nextcloud for file storage. I also believe it is the best open source alternative, but deep down it
+feels laggy and too much bloated for personal use. I would prefer something very minimal that solely works as a file
+server and explore and nothing else. Similarly, with ebooks, Calibre is good, but it feels outdated.
+
+If you do have some great suggestions, please put them in comments down below. You can use GitHub sign in or put an
+anonymous comment.
@@ -0,0 +1,3 @@
+---
+draft: true
+---
@@ -0,0 +1,3 @@
+---
+draft: true
+---
@@ -0,0 +1,60 @@
+baseURL: 'https://avinal.space/'
+languageCode: en-us
+title: Fedoraemon
+menus:
+  main:
+    - name: Home
+      pageRef: /
+      weight: 10
+    - name: Posts
+      pageRef: /posts
+      weight: 20
+    - name: Tags
+      pageRef: /tags
+      weight: 30
+module:
+  hugoVersion:
+    extended: false
+    min: 0.116.0
+
+params:
+  showWordCount: true
+  showReadingTime: true
+  toc: true
+  numberedSubtitles: true
+  navs:
+    - name: Home
+      link: https://avinal.space
+    - name: About
+      link: https://avinal.space/pages/about-me
+    - name: Blog
+      link: https://avinal.space/posts
+    - name: Projects
+      link: https://avinal.space/pages/projects
+    - name: GitHub
+      link: https://github.com/avinal
+
+disableKinds: ["home", "taxonomy"]
+
+taxonomies:
+  category: category
+  tag: tags
+
+permalinks:
+  tags: "/posts/tags/:slug"
+  category: "/posts/category/:slug"
+
+markup:
+  highlight:
+    anchorLineNos: false
+    # codeFences: true
+    guessSyntax: false
+    lineNoStart: 1
+    # lineNos: true 
+    # lineNumbersInTable: true
+    noClasses: true
+    noHl: false
+    style: base16-snazzy
+  goldmark:
+    renderer:
+      unsafe: true
@@ -0,0 +1,3 @@
+<h{{ .Level }} id="{{ .Anchor | safeURL }}">{{ .Text | safeHTML }}
+    <a href="#{{ .Anchor | safeURL }}">#</a>
+</h{{ .Level }}>
@@ -0,0 +1,18 @@
+<!DOCTYPE html>
+<html lang="{{ or site.Language.LanguageCode site.Language.Lang }}"
+  dir="{{ or site.Language.LanguageDirection `ltr` }}">
+
+<head>
+  {{ partial "head.html" . }}
+</head>
+
+<body class="bg-neutral-800">
+  <main class="container mx-auto">
+    {{ block "main" . }}{{ end }}
+    <footer>
+      {{ partial "footer.html" . }}
+    </footer>
+  </main>
+</body>
+
+</html>
@@ -0,0 +1,7 @@
+{{ define "main" }}
+  {{ .Content }}
+  {{ range site.RegularPages }}
+    <h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
+    {{ .Summary }}
+  {{ end }}
+{{ end }}
@@ -0,0 +1,78 @@
+{{ define "main" }}
+<div
+  class="prose prose-invert mx-auto prose-lg prose-a:decoration-cyan-500 hover:prose-a:decoration-pink-500 text-white">
+  <div class="md:-mx-8 lg:-mx-16 px-8 py-1">
+    <h1 class="text-5xl font-bold mb-6 mt-12 text-center">{{ .Title }}</h1>
+
+    {{ .Content }}
+  </div>
+</div>
+<section class="text-gray-100">
+  <div class="max-w-6xl p-6 mx-auto space-y-6 sm:space-y-12 mb-16">
+    {{ range first 1 .Pages }}
+    <div
+      class="block max-x-sm gap-3 mx-auto sm:max-w-full group hover:no-underline focus:no-underline lg:grid lg:grid-cols-12 bg-neutral-900">
+      <a class="lg:col-span-7" href="{{ .RelPermalink }}">
+        <img class="object-cover w-full h-64 rounded sm:h-96 lg:col-span-7" src="{{ .Params.Image | absURL }}"
+          alt="{{ .LinkTitle }}">
+      </a>
+      <div class="p-6 space-y-2 lg:col-span-5">
+        <a href="{{ .RelPermalink }}">
+          <h3 class="text-2xl font-semibold sm:text-4xl group-hover:underline group-focus:underline">{{ .LinkTitle }}
+          </h3>
+          {{ $dateMachine := .Date | time.Format "2006-01-02T15:04:05-07:00" }}
+          {{ $dateHuman := .Date | time.Format ":date_long" }}
+          <time datetime="{{ $dateMachine }}" class="text-gray-400">{{ $dateHuman }}</time>
+          {{ if gt .ReadingTime 1 }}
+          {{ .Scratch.Set "timeUnit" "mins" }}
+          {{ else }}
+          {{ .Scratch.Set "timeUnit" "min" }}
+          {{ end }}
+
+          {{ if .Site.Params.showReadingTime }}
+          <span class="text-gray-400"> | ~{{.ReadingTime}} {{ .Scratch.Get "timeUnit" }}</span>
+          {{ end }}
+          <p> {{ .Summary | truncate 250 }}</p>
+        </a>
+          <span class="flex flex-wrap py-6 space-x-2">
+            <a class="px-3 py-1 m-1 rounded-sm hover:underline bg-pink-400 text-gray-900 font-bold" href="/posts/category/{{ .Params.Category }}">
+              {{ .Params.Category }}</a>
+          </span>
+      </div>
+    </div>
+    {{ end }}
+    <div class="grid justify-center grid-cols-1 gap-6 sm:grid-cols-2 lg:grid-cols-3">
+      {{ range after 1 .Pages }}
+      <div class="max-w-sm mx-auto group hover:no-underline focus:no-underline bg-neutral-900">
+        <a href="{{ .RelPermalink }}">
+          <img class="object-cover w-full h-44 rounded" src="{{ .Params.Image | absURL }}" alt="{{ .LinkTitle }}">
+        </a>
+        <div class="p-6 space-y-2">
+          <a href="{{ .RelPermalink }}">
+            <h3 class="text-2xl font-semibold group-hover:underline group-focus:underline">{{ .LinkTitle }}</h3>
+            {{ $dateMachine := .Date | time.Format "2006-01-02T15:04:05-07:00" }}
+            {{ $dateHuman := .Date | time.Format ":date_long" }}
+            <time datetime="{{ $dateMachine }}" class="text-gray-400">{{ $dateHuman }}</time>
+            {{ if gt .ReadingTime 1 }}
+            {{ .Scratch.Set "timeUnit" "mins" }}
+            {{ else }}
+            {{ .Scratch.Set "timeUnit" "min" }}
+            {{ end }}
+
+            {{ if .Site.Params.showReadingTime }}
+            <span class="text-gray-400"> | ~{{.ReadingTime}} {{ .Scratch.Get "timeUnit" }}</span>
+            {{ end }}
+            <p> {{ .Summary | truncate 150 }}</p>
+
+          </a>
+            <span class="flex flex-wrap py-6 space-x-2">
+              <a class="px-3 py-1 m-1 rounded-sm hover:underline bg-pink-400 text-gray-900 font-bold" href="/posts/category/{{ .Params.Category }}">
+                {{ .Params.Category }}</a>
+            </span>
+        </div>
+      </div>
+      {{ end }}
+    </div>
+  </div>
+</section>
+{{ end }}
@@ -0,0 +1,32 @@
+{{ define "main" }}
+<div class="min-h-screen flex flex-col justify-center relative overflow-hidden">
+  <div class="relative w-full bg-neutral md:max-w-3xl md:mx-auto lg:max-w-4xl lg:pb-28">
+
+    <div class="prose prose-invert mx-auto prose-lg prose-a:decoration-cyan-500 hover:prose-a:decoration-pink-500">
+      <div class="bg-neutral-900 md:-mx-8 lg:-mx-16 px-8 py-1">
+
+        {{ partial "header.html" . }}
+
+        <article>
+          {{ if cond (ne .Params.toc nil) .Params.toc .Site.Params.toc }}
+          {{ if ne .TableOfContents "<nav id=\"TableOfContents\"></nav>" }}
+          <details class="open:bg-neutral-800 open:border open:rounded open:border-cyan-700  ">
+            <summary>
+              <b>In this post, we'll take a look at:</b>
+            </summary>
+            <div class="toc {{ if .Site.Params.numberedSubtitles }}numbered-subtitles{{ end }} ">{{ .TableOfContents }}
+            </div>
+          </details>
+          {{ end }}
+          {{ end }}
+
+          {{ .Content }}
+        </article>
+
+        {{ partial "terms.html" (dict "taxonomy" "tags" "page" .) }}
+      </div>
+    </div>
+    {{ partial "comments.html" . (dict "taxonomy" "tags" "page" .) }}
+  </div>
+</div>
+{{ end }}
@@ -0,0 +1,18 @@
+<script>
+  !(function (e, n) {
+    for (var o = 0; o < e.length; o++) {
+      var r = n.createElement("script"),
+        c = ".js",
+        d = n.head || n.body;
+      "noModule" in r
+        ? ((r.type = "module"), (c = ".mjs"))
+        : (r.async = !0),
+        (r.defer = !0),
+        (r.src = remark_config.host + "/web/" + e[o] + c),
+        d.appendChild(r);
+    }
+  })(remark_config.components || ["embed"], document);
+</script>
+
+<div id="remark42" class="md:p-4 mb-16"></div>
+
@@ -0,0 +1,8 @@
+<div class="fixed bottom-0 left-0 bg-neutral-900 p-3 w-full border-t border-cyan-500">
+    <div class="mx-auto flex justify-center space-x-6 text-gray-400">
+        {{ range .Site.Params.navs }}
+        <a class="underline decoration-cyan-500 hover:decoration-pink-500 text-xl" href="{{ .link | safeURL }}">{{ .name
+            }}</a>
+        {{ end }}
+    </div>
+</div>
@@ -0,0 +1,28 @@
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<title itemprop="name">{{ if .IsHome }}{{ site.Title }}{{ else }}{{ printf "%s | %s" .Title site.Title }}{{ end }}
+</title>
+{{ if eq .Section "posts" }}
+<meta property="og:title" content="{{ .Title }} | {{ .Site.Title }}" />
+<meta name="twitter:title" content="{{ .Title }} | {{ .Site.Title }}" />
+<meta itemprop="name" content="{{ .Title }} | {{ .Site.Title }}" />
+<meta name="application-name" content="{{ .Title }} | {{ .Site.Title }}" />
+<meta property="og:site_name" content="{{ .Site.Params.sitename }}" />
+<meta name="description" content="{{ .Params.description }}" />
+<meta itemprop="description" content="{{ .Params.description }}" />
+<meta property="og:description" content="{{ .Params.description }}" />
+<meta name="twitter:description" content="{{ .Params.description }}" />
+{{ with .Params.image }}
+<meta itemprop="image" content="{{ . | absURL }}" />
+<meta property="og:image" content="{{ . | absURL }}" />
+<meta name="twitter:image" content="{{ . | absURL }}" />
+<meta name="twitter:image:src" content="{{ . | absURL }}" />
+{{ else }}
+<meta itemprop="image" content="{{ .Site.Params.ogimage | absURL }}" />
+<meta property="og:image" content="{{ .Site.Params.ogimage | absURL }}" />
+<meta name="twitter:image" content="{{ .Site.Params.ogimage | absURL }}" />
+<meta name="twitter:image:src" content="{{ .Site.Params.ogimage | absURL }}" />
+{{ end }}
+{{ end }}
+{{ partialCached "head/css.html" . }}
+{{ partialCached "head/js.html" . }}
@@ -0,0 +1,9 @@
+{{- with resources.Get "css/main.css" }}
+  {{- if eq hugo.Environment "development" }}
+    <link rel="stylesheet" href="{{ .RelPermalink }}">
+  {{- else }}
+    {{- with . | minify | fingerprint }}
+      <link rel="stylesheet" href="{{ .RelPermalink }}" integrity="{{ .Data.Integrity }}" crossorigin="anonymous">
+    {{- end }}
+  {{- end }}
+{{- end }}
@@ -0,0 +1,12 @@
+{{- with resources.Get "js/main.js" }}
+  {{- if eq hugo.Environment "development" }}
+    {{- with . | js.Build }}
+      <script src="{{ .RelPermalink }}"></script>
+    {{- end }}
+  {{- else }}
+    {{- $opts := dict "minify" true }}
+    {{- with . | js.Build $opts | fingerprint }}
+      <script src="{{ .RelPermalink }}" integrity="{{- .Data.Integrity }}" crossorigin="anonymous"></script>
+    {{- end }}
+  {{- end }}
+{{- end }}
@@ -0,0 +1,25 @@
+<header class="relative">
+<img class="object-cover w-full h-60 sm:h-96 brightness-50" src="{{ .Params.Image | absURL }}" alt="{{ .Title }}">
+<h1 class="absolute top-1/2 left-1/2 -translate-x-1/2 -translate-y-1/2 text-center w-full text-white">{{ .Title }}</h1>
+
+<span class="absolute bottom-1/4 left-1/2 -translate-x-1/2 text-base font-sans oldstyle-nums text-center w-full">
+  <a class="font-bold no-underline hover:text-pink-500" href="/">Avinal Kumar</a>
+  |
+  {{ $dateMachine := .Date | time.Format "2006-01-02T15:04:05-07:00" }}
+  {{ $dateHuman := .Date | time.Format ":date_long" }}
+  <time datetime="{{ $dateMachine }}">{{ $dateHuman }}</time>
+  {{ if .Site.Params.showWordCount }}
+  <span>| {{ .WordCount }} words</span>
+  {{ end }}
+
+  {{ if gt .ReadingTime 1 }}
+  {{ .Scratch.Set "timeUnit" "mins" }}
+  {{ else }}
+  {{ .Scratch.Set "timeUnit" "min" }}
+  {{ end }}
+
+  {{ if .Site.Params.showReadingTime }}
+  <span>| ~{{.ReadingTime}} {{ .Scratch.Get "timeUnit" }}</span>
+  {{ end }}
+</span>
+</header>
@@ -0,0 +1,51 @@
+{{- /*
+Renders a menu for the given menu ID.
+
+@context {page} page The current page.
+@context {string} menuID The menu ID.
+
+@example: {{ partial "menu.html" (dict "menuID" "main" "page" .) }}
+*/}}
+
+{{- $page := .page }}
+{{- $menuID := .menuID }}
+
+{{- with index site.Menus $menuID }}
+  <nav>
+    <ul>
+      {{- partial "inline/menu/walk.html" (dict "page" $page "menuEntries" .) }}
+    </ul>
+  </nav>
+{{- end }}
+
+{{- define "partials/inline/menu/walk.html" }}
+  {{- $page := .page }}
+  {{- range .menuEntries }}
+    {{- $attrs := dict "href" .URL }}
+    {{- if $page.IsMenuCurrent .Menu . }}
+      {{- $attrs = merge $attrs (dict "class" "active" "aria-current" "page") }}
+    {{- else if $page.HasMenuCurrent .Menu .}}
+      {{- $attrs = merge $attrs (dict "class" "ancestor" "aria-current" "true") }}
+    {{- end }}
+    {{- $name := .Name }}
+    {{- with .Identifier }}
+      {{- with T . }}
+        {{- $name = . }}
+      {{- end }}
+    {{- end }}
+    <li>
+      <a
+        {{- range $k, $v := $attrs }}
+          {{- with $v }}
+            {{- printf " %s=%q" $k $v | safeHTMLAttr }}
+          {{- end }}
+        {{- end -}}
+      >{{ $name }}</a>
+      {{- with .Children }}
+        <ul>
+          {{- partial "inline/menu/walk.html" (dict "page" $page "menuEntries" .) }}
+        </ul>
+      {{- end }}
+    </li>
+  {{- end }}
+{{- end }}
@@ -0,0 +1,22 @@
+{{- /*
+For a given taxonomy, renders a list of terms assigned to the page.
+
+@context {page} page The current page.
+@context {string} taxonomy The taxonony.
+
+@example: {{ partial "terms.html" (dict "taxonomy" "tags" "page" .) }}
+*/}}
+
+{{- $page := .page }}
+{{- $taxonomy := .taxonomy }}
+
+{{- with $page.GetTerms $taxonomy }}
+{{- $label := (index . 0).Parent.LinkTitle }}
+<span class="flex flex-wrap py-6 space-x-2 border-t border-gray-500">
+  <!-- <a class="px-3 py-1 m-1 rounded-sm hover:underline bg-pink-400 text-gray-900 font-bold" href="/category/"></a> -->
+  {{- range . }}
+  <a class="px-3 py-1 m-1 rounded-sm bg-cyan-500 text-gray-900" href="{{ .RelPermalink }}">#{{ .LinkTitle }}</a>
+  {{- end }}
+</span>
+{{- end }}
+
@@ -0,0 +1,545 @@
+/*
+! tailwindcss v3.3.6 | MIT License | https://tailwindcss.com
+*/
+
+/*
+1. Prevent padding and border from affecting element width. (https://github.com/mozdevs/cssremedy/issues/4)
+2. Allow adding a border to an element by just adding a border-width. (https://github.com/tailwindcss/tailwindcss/pull/116)
+*/
+
+*,
+::before,
+::after {
+  box-sizing: border-box;
+  /* 1 */
+  border-width: 0;
+  /* 2 */
+  border-style: solid;
+  /* 2 */
+  border-color: #e5e7eb;
+  /* 2 */
+}
+
+::before,
+::after {
+  --tw-content: '';
+}
+
+/*
+1. Use a consistent sensible line-height in all browsers.
+2. Prevent adjustments of font size after orientation changes in iOS.
+3. Use a more readable tab size.
+4. Use the user's configured `sans` font-family by default.
+5. Use the user's configured `sans` font-feature-settings by default.
+6. Use the user's configured `sans` font-variation-settings by default.
+*/
+
+html {
+  line-height: 1.5;
+  /* 1 */
+  -webkit-text-size-adjust: 100%;
+  /* 2 */
+  -moz-tab-size: 4;
+  /* 3 */
+  -o-tab-size: 4;
+     tab-size: 4;
+  /* 3 */
+  font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, "Noto Sans", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";
+  /* 4 */
+  font-feature-settings: normal;
+  /* 5 */
+  font-variation-settings: normal;
+  /* 6 */
+}
+
+/*
+1. Remove the margin in all browsers.
+2. Inherit line-height from `html` so users can set them as a class directly on the `html` element.
+*/
+
+body {
+  margin: 0;
+  /* 1 */
+  line-height: inherit;
+  /* 2 */
+}
+
+/*
+1. Add the correct height in Firefox.
+2. Correct the inheritance of border color in Firefox. (https://bugzilla.mozilla.org/show_bug.cgi?id=190655)
+3. Ensure horizontal rules are visible by default.
+*/
+
+hr {
+  height: 0;
+  /* 1 */
+  color: inherit;
+  /* 2 */
+  border-top-width: 1px;
+  /* 3 */
+}
+
+/*
+Add the correct text decoration in Chrome, Edge, and Safari.
+*/
+
+abbr:where([title]) {
+  -webkit-text-decoration: underline dotted;
+          text-decoration: underline dotted;
+}
+
+/*
+Remove the default font size and weight for headings.
+*/
+
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+  font-size: inherit;
+  font-weight: inherit;
+}
+
+/*
+Reset links to optimize for opt-in styling instead of opt-out.
+*/
+
+a {
+  color: inherit;
+  text-decoration: inherit;
+}
+
+/*
+Add the correct font weight in Edge and Safari.
+*/
+
+b,
+strong {
+  font-weight: bolder;
+}
+
+/*
+1. Use the user's configured `mono` font-family by default.
+2. Use the user's configured `mono` font-feature-settings by default.
+3. Use the user's configured `mono` font-variation-settings by default.
+4. Correct the odd `em` font sizing in all browsers.
+*/
+
+code,
+kbd,
+samp,
+pre {
+  font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace;
+  /* 1 */
+  font-feature-settings: normal;
+  /* 2 */
+  font-variation-settings: normal;
+  /* 3 */
+  font-size: 1em;
+  /* 4 */
+}
+
+/*
+Add the correct font size in all browsers.
+*/
+
+small {
+  font-size: 80%;
+}
+
+/*
+Prevent `sub` and `sup` elements from affecting the line height in all browsers.
+*/
+
+sub,
+sup {
+  font-size: 75%;
+  line-height: 0;
+  position: relative;
+  vertical-align: baseline;
+}
+
+sub {
+  bottom: -0.25em;
+}
+
+sup {
+  top: -0.5em;
+}
+
+/*
+1. Remove text indentation from table contents in Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=999088, https://bugs.webkit.org/show_bug.cgi?id=201297)
+2. Correct table border color inheritance in all Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=935729, https://bugs.webkit.org/show_bug.cgi?id=195016)
+3. Remove gaps between table borders by default.
+*/
+
+table {
+  text-indent: 0;
+  /* 1 */
+  border-color: inherit;
+  /* 2 */
+  border-collapse: collapse;
+  /* 3 */
+}
+
+/*
+1. Change the font styles in all browsers.
+2. Remove the margin in Firefox and Safari.
+3. Remove default padding in all browsers.
+*/
+
+button,
+input,
+optgroup,
+select,
+textarea {
+  font-family: inherit;
+  /* 1 */
+  font-feature-settings: inherit;
+  /* 1 */
+  font-variation-settings: inherit;
+  /* 1 */
+  font-size: 100%;
+  /* 1 */
+  font-weight: inherit;
+  /* 1 */
+  line-height: inherit;
+  /* 1 */
+  color: inherit;
+  /* 1 */
+  margin: 0;
+  /* 2 */
+  padding: 0;
+  /* 3 */
+}
+
+/*
+Remove the inheritance of text transform in Edge and Firefox.
+*/
+
+button,
+select {
+  text-transform: none;
+}
+
+/*
+1. Correct the inability to style clickable types in iOS and Safari.
+2. Remove default button styles.
+*/
+
+button,
+[type='button'],
+[type='reset'],
+[type='submit'] {
+  -webkit-appearance: button;
+  /* 1 */
+  background-color: transparent;
+  /* 2 */
+  background-image: none;
+  /* 2 */
+}
+
+/*
+Use the modern Firefox focus style for all focusable elements.
+*/
+
+:-moz-focusring {
+  outline: auto;
+}
+
+/*
+Remove the additional `:invalid` styles in Firefox. (https://github.com/mozilla/gecko-dev/blob/2f9eacd9d3d995c937b4251a5557d95d494c9be1/layout/style/res/forms.css#L728-L737)
+*/
+
+:-moz-ui-invalid {
+  box-shadow: none;
+}
+
+/*
+Add the correct vertical alignment in Chrome and Firefox.
+*/
+
+progress {
+  vertical-align: baseline;
+}
+
+/*
+Correct the cursor style of increment and decrement buttons in Safari.
+*/
+
+::-webkit-inner-spin-button,
+::-webkit-outer-spin-button {
+  height: auto;
+}
+
+/*
+1. Correct the odd appearance in Chrome and Safari.
+2. Correct the outline style in Safari.
+*/
+
+[type='search'] {
+  -webkit-appearance: textfield;
+  /* 1 */
+  outline-offset: -2px;
+  /* 2 */
+}
+
+/*
+Remove the inner padding in Chrome and Safari on macOS.
+*/
+
+::-webkit-search-decoration {
+  -webkit-appearance: none;
+}
+
+/*
+1. Correct the inability to style clickable types in iOS and Safari.
+2. Change font properties to `inherit` in Safari.
+*/
+
+::-webkit-file-upload-button {
+  -webkit-appearance: button;
+  /* 1 */
+  font: inherit;
+  /* 2 */
+}
+
+/*
+Add the correct display in Chrome and Safari.
+*/
+
+summary {
+  display: list-item;
+}
+
+/*
+Removes the default spacing and border for appropriate elements.
+*/
+
+blockquote,
+dl,
+dd,
+h1,
+h2,
+h3,
+h4,
+h5,
+h6,
+hr,
+figure,
+p,
+pre {
+  margin: 0;
+}
+
+fieldset {
+  margin: 0;
+  padding: 0;
+}
+
+legend {
+  padding: 0;
+}
+
+ol,
+ul,
+menu {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+}
+
+/*
+Reset default styling for dialogs.
+*/
+
+dialog {
+  padding: 0;
+}
+
+/*
+Prevent resizing textareas horizontally by default.
+*/
+
+textarea {
+  resize: vertical;
+}
+
+/*
+1. Reset the default placeholder opacity in Firefox. (https://github.com/tailwindlabs/tailwindcss/issues/3300)
+2. Set the default placeholder color to the user's configured gray 400 color.
+*/
+
+input::-moz-placeholder, textarea::-moz-placeholder {
+  opacity: 1;
+  /* 1 */
+  color: #9ca3af;
+  /* 2 */
+}
+
+input::placeholder,
+textarea::placeholder {
+  opacity: 1;
+  /* 1 */
+  color: #9ca3af;
+  /* 2 */
+}
+
+/*
+Set the default cursor for buttons.
+*/
+
+button,
+[role="button"] {
+  cursor: pointer;
+}
+
+/*
+Make sure disabled buttons don't get the pointer cursor.
+*/
+
+:disabled {
+  cursor: default;
+}
+
+/*
+1. Make replaced elements `display: block` by default. (https://github.com/mozdevs/cssremedy/issues/14)
+2. Add `vertical-align: middle` to align replaced elements more sensibly by default. (https://github.com/jensimmons/cssremedy/issues/14#issuecomment-634934210)
+   This can trigger a poorly considered lint error in some tools but is included by design.
+*/
+
+img,
+svg,
+video,
+canvas,
+audio,
+iframe,
+embed,
+object {
+  display: block;
+  /* 1 */
+  vertical-align: middle;
+  /* 2 */
+}
+
+/*
+Constrain images and videos to the parent width and preserve their intrinsic aspect ratio. (https://github.com/mozdevs/cssremedy/issues/14)
+*/
+
+img,
+video {
+  max-width: 100%;
+  height: auto;
+}
+
+/* Make elements with the HTML hidden attribute stay hidden by default */
+
+[hidden] {
+  display: none;
+}
+
+*, ::before, ::after {
+  --tw-border-spacing-x: 0;
+  --tw-border-spacing-y: 0;
+  --tw-translate-x: 0;
+  --tw-translate-y: 0;
+  --tw-rotate: 0;
+  --tw-skew-x: 0;
+  --tw-skew-y: 0;
+  --tw-scale-x: 1;
+  --tw-scale-y: 1;
+  --tw-pan-x:  ;
+  --tw-pan-y:  ;
+  --tw-pinch-zoom:  ;
+  --tw-scroll-snap-strictness: proximity;
+  --tw-gradient-from-position:  ;
+  --tw-gradient-via-position:  ;
+  --tw-gradient-to-position:  ;
+  --tw-ordinal:  ;
+  --tw-slashed-zero:  ;
+  --tw-numeric-figure:  ;
+  --tw-numeric-spacing:  ;
+  --tw-numeric-fraction:  ;
+  --tw-ring-inset:  ;
+  --tw-ring-offset-width: 0px;
+  --tw-ring-offset-color: #fff;
+  --tw-ring-color: rgb(59 130 246 / 0.5);
+  --tw-ring-offset-shadow: 0 0 #0000;
+  --tw-ring-shadow: 0 0 #0000;
+  --tw-shadow: 0 0 #0000;
+  --tw-shadow-colored: 0 0 #0000;
+  --tw-blur:  ;
+  --tw-brightness:  ;
+  --tw-contrast:  ;
+  --tw-grayscale:  ;
+  --tw-hue-rotate:  ;
+  --tw-invert:  ;
+  --tw-saturate:  ;
+  --tw-sepia:  ;
+  --tw-drop-shadow:  ;
+  --tw-backdrop-blur:  ;
+  --tw-backdrop-brightness:  ;
+  --tw-backdrop-contrast:  ;
+  --tw-backdrop-grayscale:  ;
+  --tw-backdrop-hue-rotate:  ;
+  --tw-backdrop-invert:  ;
+  --tw-backdrop-opacity:  ;
+  --tw-backdrop-saturate:  ;
+  --tw-backdrop-sepia:  ;
+}
+
+::backdrop {
+  --tw-border-spacing-x: 0;
+  --tw-border-spacing-y: 0;
+  --tw-translate-x: 0;
+  --tw-translate-y: 0;
+  --tw-rotate: 0;
+  --tw-skew-x: 0;
+  --tw-skew-y: 0;
+  --tw-scale-x: 1;
+  --tw-scale-y: 1;
+  --tw-pan-x:  ;
+  --tw-pan-y:  ;
+  --tw-pinch-zoom:  ;
+  --tw-scroll-snap-strictness: proximity;
+  --tw-gradient-from-position:  ;
+  --tw-gradient-via-position:  ;
+  --tw-gradient-to-position:  ;
+  --tw-ordinal:  ;
+  --tw-slashed-zero:  ;
+  --tw-numeric-figure:  ;
+  --tw-numeric-spacing:  ;
+  --tw-numeric-fraction:  ;
+  --tw-ring-inset:  ;
+  --tw-ring-offset-width: 0px;
+  --tw-ring-offset-color: #fff;
+  --tw-ring-color: rgb(59 130 246 / 0.5);
+  --tw-ring-offset-shadow: 0 0 #0000;
+  --tw-ring-shadow: 0 0 #0000;
+  --tw-shadow: 0 0 #0000;
+  --tw-shadow-colored: 0 0 #0000;
+  --tw-blur:  ;
+  --tw-brightness:  ;
+  --tw-contrast:  ;
+  --tw-grayscale:  ;
+  --tw-hue-rotate:  ;
+  --tw-invert:  ;
+  --tw-saturate:  ;
+  --tw-sepia:  ;
+  --tw-drop-shadow:  ;
+  --tw-backdrop-blur:  ;
+  --tw-backdrop-brightness:  ;
+  --tw-backdrop-contrast:  ;
+  --tw-backdrop-grayscale:  ;
+  --tw-backdrop-hue-rotate:  ;
+  --tw-backdrop-invert:  ;
+  --tw-backdrop-opacity:  ;
+  --tw-backdrop-saturate:  ;
+  --tw-backdrop-sepia:  ;
+}
+
+.block {
+  display: block;
+}
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
avinal	1bb34a512a	typo fixes and improvements Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED	2024-12-02 01:59:21 +05:30
avinal	84d922ffdf	blog: how to grow lilies Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED	2024-12-02 01:49:41 +05:30
avinal	ac07c6d551	fix typo and update packages	2024-09-26 13:02:44 +05:30
avinal	7de0552895	fix typo	2024-09-25 21:43:18 +05:30
avinal	9fed144245	added new blog on grapheneos Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2024-09-25 20:39:32 +05:30
ImgBotApp	8a7416e5b9	[ImgBot] Optimize images *Total -- 781.64kb -> 710.13kb (9.15%) /blog/static/images/terminal-workspace.png -- 606.07kb -> 539.92kb (10.91%) /blog/static/images/dog-using-terminal.jpg -- 175.57kb -> 170.21kb (3.05%) Signed-off-by: ImgBotApp <ImgBotHelp@gmail.com>	2024-06-08 15:55:55 +05:30
avinal	7a3399a795	add terminal workspace screenshot Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2024-06-08 13:14:11 +05:30
avinal	0dbf1345c5	correct time issue and update packages Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2024-06-08 03:04:59 +05:30
avinal	26d4777488	add new blog on terminal tools Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-06-08 02:31:24 +05:30
avinal	1b32720c8c	update npm packages Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-04-29 23:28:24 +05:30
avinal	775ed4cb2a	add a new post Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-04-29 23:21:09 +05:30
ImgBotApp	01c8389e7f	[ImgBot] Optimize images *Total -- 3,477.76kb -> 3,447.78kb (0.86%) /blog/static/images/redhat_logo.png -- 7.03kb -> 3.08kb (56.11%) /blog/static/images/mks_logo.png -- 14.28kb -> 7.63kb (46.57%) /static/logo-loading.svg -- 1.57kb -> 1.06kb (32.26%) /blog/static/images/goladder.png -- 20.96kb -> 17.21kb (17.9%) /static/logo-static.svg -- 0.51kb -> 0.49kb (4.17%) /blog/static/images/avinal-meta.png -- 951.75kb -> 938.03kb (1.44%) /static/apple-touch-icon.png -- 5.88kb -> 5.83kb (0.83%) /blog/static/images/venus-flytrap.gif -- 2,475.78kb -> 2,474.44kb (0.05%) Signed-off-by: ImgBotApp <ImgBotHelp@gmail.com>	2024-04-01 07:26:01 +00:00
avinal	35ec52b22f	remove image copy Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-31 12:18:23 +05:30
avinal	1e13894242	fix perf issues Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-31 12:09:15 +05:30
avinal	31a90cd19c	reduce image size Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-31 05:59:33 +00:00
avinal	c36e86ba2f	update website Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-31 05:59:33 +00:00
avinal	05c967c5a8	fix homepage links and update information Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 13:36:20 +05:30
avinal	d2c0f902d1	fix links and github action Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 13:20:30 +05:30
avinal	d085c84d03	fix links and add image Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 13:06:18 +05:30
avinal	91d3d5df19	fix template Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:55:23 +05:30
avinal	c8a95c9706	update netlify Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:52:07 +05:30
avinal	4bcef023c0	remove null deploy Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:48:20 +05:30
avinal	8d88cf03c4	update npm modules Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:47:13 +05:30
avinal	a196ac4391	added hugo website Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:44:19 +05:30
avinal	1c20213cd4	remove blogs from elm, switch to hugo Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:42:14 +05:30
avinal	5a21dd69a8	move content to blog directory Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:41:22 +05:30
avinal	e9ab9932be	remove html-only site Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com> rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED	2024-03-30 12:39:30 +05:30
avinal	3145afbf52	update netlify Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2024-01-21 21:59:01 +05:30
avinal	f9d2b58db3	check concept Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2024-01-21 21:50:44 +05:30
avinal	046ad24d97	update about page Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-09-30 20:51:59 +05:30
avinal	26a9b72dff	fix highlighting Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-09-30 12:31:37 +05:30
avinal	531a3c7f55	bump elm-land Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-09-26 20:25:21 +05:30
avinal	ce8f46553c	add new blog on logitech mouse Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-09-26 20:22:54 +05:30
avinal	222be5e44d	fix date errors Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-09-26 20:19:31 +05:30
avinal	c7da3e3388	fix sitemap	2023-07-20 20:35:22 +05:30
avinal	77ef0f8191	fix sitemap	2023-07-20 00:33:49 +05:30
avinal	2f0037ac98	add entry and image	2023-07-20 00:31:51 +05:30
avinal	38bcfeead3	add new blog	2023-07-19 20:27:18 +05:30
avinal	1168062168	page improvements	2023-07-19 16:49:00 +05:30
avinal	a2cff8b6e0	remove concurrent build and add 404	2023-07-19 16:18:51 +05:30
avinal	2afb4b65b8	minor fixes	2023-07-19 15:58:47 +05:30
avinal	0bb902369f	update sitemap	2023-07-19 15:53:12 +05:30
avinal	047aeb0b86	remove submodule and apply theme	2023-07-19 15:53:08 +05:30
avinal	f4c5db16d2	Delete html-only/themes directory Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-07-19 03:29:26 +05:30
Avinal Kumar	8836b83c27	Update .gitmodules	2023-07-19 03:21:27 +05:30
avinal	da864f840d	change submodule	2023-07-19 00:01:37 +05:30
avinal	6365554a4f	build and deploy for hugo	2023-07-18 23:35:32 +05:30
avinal	a14f70123f	change links to relative	2023-07-18 23:35:11 +05:30
avinal	5ebdf00472	time format improvements and word count	2023-07-18 23:34:46 +05:30
avinal	660f227a8f	miscellaneous	2023-07-18 23:27:25 +05:30
avinal	97fdd892d5	fix and format frontmatter	2023-07-18 23:26:53 +05:30
avinal	b5cea84e4d	add hugo	2023-07-18 23:24:58 +05:30
avinal	82d2b002e0	add theme submodule Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-07-18 13:41:35 +05:30
avinal	4d49130e9c	bump elm-land to 0.19.1 Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-07-02 18:27:25 +05:30
avinal	fcf7bc3ed3	add comment system to the blogs Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-18 23:03:05 +05:30
avinal	421bb616ec	add about-me page and notfound page Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-14 19:27:13 +05:30
avinal	b20d3de614	change time formatting Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-14 19:26:05 +05:30
avinal	35dc64bbbf	fix yaml parsing error Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-14 19:24:31 +05:30
avinal	b14eadbd6e	add line numbers for code blocks Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-02 14:18:38 +05:30
avinal	05e332c727	fix image for proposal Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-01 19:35:15 +05:30
avinal	656e8277f9	fix error in url and add new blog to sitemap Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-01 19:20:11 +05:30
avinal	2d6f7f929f	change appearance of the posts Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-01 19:16:19 +05:30
avinal	1fd232f751	remove redundant title from all the posts Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-04-01 19:15:02 +05:30
avinal	0851835bc9	add Gsoc proposal Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-03-30 21:29:21 +05:30
avinal	79ce59b499	dynamically updating mets tags Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-03-28 14:59:25 +05:30
avinal	e6753e137d	minor performance improvements Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-03-28 14:13:20 +05:30
avinal	8e3d4b408f	add tekton results blog Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-03-28 14:11:55 +05:30
avinal	7e8dd5cdea	fix image positioning Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-02-06 01:35:22 +05:30
avinal	50c630733a	add new sitemap Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-02-06 01:34:58 +05:30
avinal	22fec59069	add robots and alt Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-31 00:50:35 +05:30
avinal	5194c4bacd	add meta tags Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-31 00:36:05 +05:30
avinal	85c3881dcd	fix hidden confirm button Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 23:57:37 +05:30
avinal	921f5ee883	add meet page and update image style Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 22:25:21 +05:30
avinal	7f4e4f5938	update posts data Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 22:24:22 +05:30
avinal	11bff197f6	add images Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 22:21:59 +05:30
avinal	eae6b0d3f7	add gsoc posts Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 22:21:36 +05:30
avinal	6ddc56d3a7	refactoring few posts Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-30 22:21:17 +05:30
avinal	dbd1dfec3a	add date parser and refactor - remove unused variables, methods - move footer into a separate folder - add date parser - add datetime Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-29 23:31:51 +05:30
avinal	c8b58f6080	add category and minor improvements Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-27 21:07:57 +05:30
avinal	c483f30cea	fix goatcounter Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 17:06:51 +05:30
avinal	c44d451467	fix issue with build Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 16:47:53 +05:30
avinal	3d99bcf3a9	update dependencies Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 16:43:48 +05:30
avinal	b827a4b0f9	cleanup and minor fixes Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 16:43:32 +05:30
avinal	c2adcaec6c	add favicons and site manifests Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 16:42:07 +05:30
avinal	9a88c34745	move articles to static Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-24 16:40:54 +05:30
avinal	43e157885f	remove unnecessary files Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-03 14:21:41 +05:30
avinal	beb5acf322	add netlify Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-03 13:32:39 +05:30
avinal	961c1897c1	remove redirection Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-03 13:31:28 +05:30
avinal	87f2c7c2fa	fix links Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 23:09:36 +05:30
avinal	9947b7580e	add botton informations Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 23:01:29 +05:30
avinal	4d7ab38808	sitemap added Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 17:03:31 +05:30
avinal	1317e9249b	Merge pull request #8 from avinal/avinal/improvements Image related improvements	2023-01-02 16:26:56 +05:30
avinal	97f9a6e955	modify page to show images Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 16:24:26 +05:30
avinal	2abc42b79e	add image links to yaml and json Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 16:21:50 +05:30
avinal	e266508040	convert all images to webp Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 16:20:13 +05:30
avinal	d0a2e82884	fix 404 redirection Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 13:03:25 +05:30
avinal	6e163ae9e1	Merge pull request #7 from avinal/avinal/elm-land-website Add elm-land website	2023-01-02 12:55:00 +05:30
avinal	9133b0ebea	fix github actions error Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:51:23 +05:30
avinal	6ee5f2f0bc	rename wsl2-move to wsl1 Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:49:28 +05:30
avinal	0b78d7a3e1	add github actions config Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:46:55 +05:30
avinal	28e6888a11	add static and content Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:45:57 +05:30
avinal	239c67da1c	add new elm-land website Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:45:21 +05:30
avinal	0097117553	remove old vanila elm website Signed-off-by: Avinal Kumar <avinal.xlvii@gmail.com>	2023-01-02 12:44:25 +05:30