Add (not currently working) settings to generate a SQL db

.drone.yml

@@ -1,41 +0,0 @@
----
-kind: pipeline
-type: docker
-name: Deploy to bbaovanc.com
-
-trigger:
-    branch:
-        - master
-    event:
-        exclude:
-            - pull_request
-
-steps:
-    - name: submodules
-      image: alpine/git
-      commands:
-          - git submodule update --init --recursive
-
-    - name: build
-      image: bbaovanc/hugo
-      commands:
-          - hugo version
-          - hugo --minify
-
-    - name: list files
-      image: alpine:latest
-      commands:
-          - find public/
-
-    - name: upload
-      image: appleboy/drone-scp
-      settings:
-          host: bbaovanc.com
-          port: 2222
-          username: droneci
-          key:
-              from_secret: SSH_KEY
-          target: /var/www/bbaovanc/blog/
-          rm: true
-          source: public/
-          strip_components: 1

.gitmodules

@@ -1,3 +1,3 @@
-[submodule "themes/hugo-bearblog"]
-	path = themes/hugo-bearblog
-	url = https://github.com/janraasch/hugo-bearblog.git
+[submodule "themes/terminal"]
+	path = themes/terminal
+	url = https://github.com/panr/hugo-theme-terminal.git

archetypes/blog.md

@@ -1,13 +0,0 @@
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = "{{ .Date }}"
-# Format date like 2006-01-02 (it gives an error if I use .Format)
-
-description = """
-Lorem ipsum
-"""
-
-tags = [
-    "",
-]
-+++

archetypes/default.md

@@ -1,8 +1,6 @@
-+++
-title = "{{ replace .Name "-" " " | title }}"
-menu = "main"
+---
+title: "{{ replace .Name "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+---
 
-description = """
-Lorem ipsum
-"""
-+++

config.toml

@@ -1,62 +1,110 @@
+baseURL = "https://bbaovanc.com/blog/"
+languageCode = "en-us"
+theme = "terminal"
+paginate = 5
+enableGitInfo = true
 
-baseURL = "https://bbaovanc.com"
+[mediaTypes]
+[mediaTypes."text/sql"]
+  suffixes = ["sql"]
 
-# The name of this wonderful theme ;-).
-theme = 'hugo-bearblog'
+[outputFormats]
+[outputFormats.SQL]
+    mediaType = "text/sql"
 
-# Basic metadata configuration for your blog.
-title = "bbaovanc's blog"
-author = "bbaovanc"
-copyright = "Copyright © 2021, bbaovanc."
-languageCode = "en-US"
+[outputs]
+    home = ["sql", "html"]
 
-# Generate a nice robots.txt for SEO
-enableRobotsTXT = true
-
-# Generate "Bearblog"-like URLs !only!, see https://bearblog.dev/.
-disableKinds = ["taxonomy"]
-ignoreErrors = ["error-disable-taxonomy"]
-[permalinks]
-  #blog = "/:slug/"
-  tags = "/blog/:slug"
+# [permalinks]
+#   posts = "/:year/:month/:title/"
 
 [params]
-  # The "description" of your website. This is used in the meta data of your generated html.
-  description = "My personal blog site"
+  # dir name of your main content (default is `content/posts`).
+  # the list of set content will show up on your index page (baseurl).
+  contentTypeName = "posts"
 
-  # The path to your "favicon". This should be a square (at least 32px x 32px) png-file.
-  # Hint: It's good practise to also put a "favicon.ico"-file into your "static"-folder.
-  favicon = "img/favicon.ico"
+  # ["orange", "blue", "red", "green", "pink"]
+  themeColor = "blue"
 
-  # These "images" are used for the structured data templates. This will show up, when
-  # services like Twitter or Slack want to generate a preview of a link to your site.
-  # See https://gohugo.io/templates/internal#twitter-cards and
-  # https://gohugo.io/templates/internal#open-graph.
-  images = ["img/favicon.png"]
+  # if you set this to 0, only submenu trigger will be visible
+  showMenuItems = 5
 
-  # Another "title" :-). This one is used as the site_name on the Hugo's internal
-  # opengraph structured data template.
-  # See https://ogp.me/ and https://gohugo.io/templates/internal#open-graph.
-  title = "bbaovanc's blog"
+  # show selector to switch language
+  showLanguageSelector = false
 
-  # This theme will, by default, inject a made-with-line at the bottom of the page.
-  # You can turn it off, but we would really appreciate if you don’t :-).
-  # hideMadeWithLine = true
+  # set theme to full screen width
+  fullWidthTheme = false
 
-  # By default, this theme displays dates with a format like "02 Jan, 2006", but
-  # you can customize it by setting the `dateFormat` param in your site's config
-  # file. See [Hugo's Format function docs](https://gohugo.io/functions/format/)
-  # for details. An example TOML config that uses [ISO
-  # 8601](https://en.wikipedia.org/wiki/ISO_8601) format:
-  # dateFormat = "2006-01-02"
+  # center theme with default width
+  centerTheme = true
 
-[menu]
-  [[menu.main]]
-    identifier = "rss"
-    name = "RSS Feed"
-    url = "/blog/index.xml"
+  # set a custom favicon (default is a `themeColor` square)
+  favicon = "icon/favicon.ico"
 
-  [[menu.main]]
-    identifier = "git-repo"
-    name = "Source Code"
-    url = "https://git.bbaovanc.com/bbaovanc.com/blog"
+  # set post to show the last updated
+  # If you use git, you can set `enableGitInfo` to `true` and then post will automatically get the last updated
+  showLastUpdated = true
+  # Provide a string as a prefix for the last update date. By default, it looks like this: 2020-xx-xx [Updated: 2020-xx-xx] :: Author
+  # updatedDatePrefix = "Updated"
+
+  # set all headings to their default size (depending on browser settings)
+  # it's set to `true` by default
+  # oneHeadingSize = false
+
+[params.twitter]
+  # set Twitter handles for Twitter cards
+  # see https://developer.twitter.com/en/docs/tweets/optimize-with-cards/guides/getting-started#card-and-content-attribution
+  # do not include @
+  creator = ""
+  site = ""
+
+[languages]
+  [languages.en]
+    languageName = "English"
+    title = "bbaovanc's blog"
+    subtitle = "My personal blog site"
+    owner = "bbaovanc"
+    keywords = ""
+    copyright = ""
+    menuMore = "Show more"
+    readMore = "Read more"
+    readOtherPosts = "Read other posts"
+    newerPosts = "Newer posts"
+    olderPosts = "Older posts"
+    missingContentMessage = "Page not found..."
+    missingBackButtonLabel = "Back to home page"
+
+    [languages.en.params.logo]
+      logoText = "bbaovanc's blog"
+      logoHomeLink = "/blog/"
+
+    [languages.en.menu]
+      [[languages.en.menu.main]]
+        identifier = "tags"
+        name = "Tags"
+        url = "/tags"
+        weight = 10
+
+      [[languages.en.menu.main]]
+        identifier = "links"
+        name = "Links"
+        url = "/links"
+        weight = 20
+
+      [[languages.en.menu.main]]
+        identifier = "rss"
+        name = "RSS Feed"
+        url = "/posts/index.xml"
+        weight = 30
+
+      [[languages.en.menu.main]]
+        identifier = "main-website"
+        name = "Main Website"
+        url = "https://bbaovanc.com/"
+        weight = 40
+
+      [[languages.en.menu.main]]
+        identifier = "source-code"
+        name = "Source Code"
+        url = "https://git.bbaovanc.com/bbaovanc.com/blog"
+        weight = 50

content/_index.md

@@ -1,3 +0,0 @@
-This is my website.
-
-https://boba.best is also my website.

content/blog/allow-non-root-processes-to-bind-to-privileged-ports.md

@@ -1,69 +0,0 @@
-+++
-title = "Allow Non Root Processes to Bind to Privileged Ports"
-date = "2021-03-28"
-aliases = [
-  "posts/allow-non-root-processes-to-bind-to-privileged-ports/",
-]
-
-description = """
-In Linux, processes cannot bind to privileged ports (<=1024) unless they are
-running as root. Here's how to allow any process to bind to privileged ports.
-"""
-
-tags = [
-  "guide",
-  "linux",
-]
-+++
-
-## Introduction
-
-In Linux, processes cannot bind to privileged ports (<=1024) unless they are
-running as root. I learned about this when I was trying to add SSH cloning to my
-[Gitea](https://gitea.io) instance. This can be bypassed by giving
-`CAP_NET_BIND_SERVICE` capabilities to either the systemd service, or the
-executable itself.
-
-## Giving `CAP_NET_BIND_SERVICE` capabilities
-
-### Using systemd (preferred)
-
-The best way is to tell systemd to give `CAP_NET_BIND_SERVICE`
-capabilities to the service. In fact, the Gitea systemd service has two
-lines[^1] that are commented out:
-
-```systemd
-CapabilityBoundingSet=CAP_NET_BIND_SERVICE
-AmbientCapabilities=CAP_NET_BIND_SERVICE
-```
-
-Uncommenting these two lines was all I had to do for Gitea.
-
-### Using `setcap`
-
-You can add `CAP_NET_BIND_SERVICE` to the executable directly using `setcap`,
-allowing it to bind to any port. Run the following command[^2]:
-
-```bash
-setcap 'cap_net_bind_service=+ep' /path/to/program
-```
-
-Note that this means that anyone with permission to run this program will be
-able to run it and bind to any privileged ports.
-
-Other caveats[^2]:
-
-> 1. You will need at least a 2.6.24 kernel
-> 2. This won't work if your file is a script. (ie, uses a #! line to launch an
->    interpreter). In this case, as far I as understand, you'd have to apply the
->    capability to the interpreter executable itself, which of course is a
->    security nightmare, since any program using that interpreter will have the
->    capability. I wasn't able to find any clean, easy way to work around this
->    problem.
-> 3. Linux will disable LD\_LIBRARY\_PATH on any program that has elevated
->    privileges like setcap or suid. So if your program uses its own .../lib/,
->    you might have to look into another option like port forwarding.
-
-[^1]: https://github.com/go-gitea/gitea/blob/3416e2a82586fca4cd452b93237b979300f55d62/contrib/systemd/gitea.service#L69
-      and https://stackoverflow.com/a/47065825
-[^2]: https://stackoverflow.com/a/414258

content/blog/new-comment-system-again.md

@@ -1,40 +0,0 @@
-+++
-title = "New Comment System (again)"
-date = "2021-04-17"
-aliases = [
-  "posts/new-comment-system-again/",
-]
-
-description = """
-I decided to switch my comment system from Isso to
-[Commento](https://www.commento.io/)
-"""
-
-tags = [
-  "announcement",
-  "hugo",
-  "blog",
-]
-+++
-
-## Isso vs Commento
-
-I know it's only been six days since I added Isso, but I decided to switch to a
-better comment system. Isso is meant to be simple, which means that it's missing
-a lot of features. Commento has a lot of features such as sticky (pinned)
-comments, spam detection, thread locking, email notifications (I couldn't get
-this working on Isso), and a nicer design. I also was able to write some
-[custom CSS rules][1] which make it look alright on my blog's theme. It also
-supports SSO, so I might add support for signing up with GitHub, and possibly
-GitLab.
-
-## Summary of the [first post]({{< ref "/blog/new-comment-system" >}})
-
-If you haven't read the
-[New Comment System]({{< ref "/blog/new-comment-system" >}}) post, here's the
-most important information. There's a comment section at the bottom of each post
-where you can view and post comments. You can post anonymously, or create an
-account so you can show your username and get email notifications. You can also
-upvote, downvote, and reply to other comments.
-
-[1]: https://git.bbaovanc.com/bbaovanc.com/blog/src/commit/478e15218313a33216d361de387b3bd878cd0ba6/assets/css/comments.css

content/blog/new-comment-system.md

@@ -1,42 +0,0 @@
-+++
-title = "New Comment System"
-date = "2021-04-11"
-aliases = [
-  "posts/new-comment-system/",
-]
-
-description = """
-I added a comment system to my blog, using [Isso](https://posativ.org/isso/).
-"""
-
-tags = [
-  "announcement",
-  "hugo",
-  "blog",
-]
-+++
-
-## About
-
-I set up a comment system named [Isso](https://posativ.org/isso/) on my blog
-today. At the bottom of each blog post, there's a comment section. You don't
-need to sign up with an account or sign in with Google, Facebook, none of that
-junk. You can comment anonymously, or provide any of the following three fields:
-name, email address, and website, which will be shown to other people viewing
-your comment. I'm going off of the assumption that no one cares/is malicious
-enough to spam my comment sections.
-
-## Known Issues
-
-### Editing and deleting not working
-
-You're supposed to be able to edit and delete comments up to 15 minutes after
-posting them. As of now, that doesn't seem to be working; the request just
-returns 403 (forbidden).
-
-### White text on white background when previewing comment
-
-This is a CSS related issue. This was also happening when editing/writing a
-comment, but I edited it so the edit box has black text. I think a better fix is
-to make the new comment form have a dark background, but I'll deal with that
-later.

content/contact.md

@@ -1,10 +0,0 @@
-+++
-title = "Contact"
-menu = "main"
-
-description = """
-List of ways to contact me
-"""
-+++
-
-- [Email me](mailto:contact@bbaovanc.com)

content/donate.md

@@ -1,18 +0,0 @@
-+++
-title = "Donate"
-menu = "main"
-
-description = """
-How to donate to me
-"""
-+++
-
-## Cryptocurrency Links
-
-Nano: `nano_1ewtme68x5gia1bjq3jx1ku5pcxzayipdxjmjrc3x8qjjpat4ria8ajhjoxd`
-
-Bitcoin: `bc1qj6h8z2tg9nxcl9ddnv9k798cru6asr6cpmj84m`
-
-Ethereum: `0x80DaED7e2BEF5d894b37fBd79d0609aa17c8Cabc`
-
-Monero: `45gGauNcWLNSobRMzk3rtfEpad7gGcEvegxCbEm6QYENdG4vag3fCVuFoKfdKSESeSEKyUNRGwAJyLaCQ6MC5AQ79DGcaRq`

content/gpg-fingerprints.md

@@ -1,17 +0,0 @@
-+++
-title = "GPG Fingerprints"
-menu = "main"
-
-description = """
-Fingerprint of my GPG key
-"""
-+++
-
-```
-sec   rsa4096 2020-08-31 [SC]
-      CB7CCED9209E47B9B99B8E1D18089E4E3CCF1D3A
-uid           [ultimate] BBaoVanC <bbaovanc@bbaovanc.com>
-uid           [ultimate] BBaoVanC <github@bbaovanc.com>
-uid           [ultimate] BBaoVanC <bbaovanc@boba.best>
-ssb   rsa4096 2020-08-31 [E]
-```

content/links.md

@@ -1,14 +1,9 @@
-+++
-title = "Links"
-menu = "main"
-aliases = [
-  "/blog/links/",
-]
+---
+title: "Links"
+toc: true
+---
 
-description = """
-Various links to my stuff
-"""
-+++
+---
 
 ## Other
 
@@ -19,8 +14,8 @@ Various links to my stuff
 - [Main Site](https://bbaovanc.com/)
 - [Blog](https://bbaovanc.com/blog/)
 - [Status Page](https://status.bbaovanc.com/)
-- [Searx Instance](https://search.bbaovanc.com/) -
-  [source code](https://github.com/BBaoVanC/searx)
+- [Searx Instance](https://searx.bbaovanc.com/) -
+  [source code](https://github.com/BBaoVanC/searx.bbaovanc.com)
 - [Gitea Instance](https://git.bbaovanc.com/)
 
 ## My Software

content/posts/checkra1n-gui-on-other-distros.md

@@ -1,25 +1,19 @@
 +++
 title = "Checkra1n GUI on Other Distros"
-date = "2021-03-25"
-aliases = [
-  "posts/checkra1n-gui-on-other-distros/",
-]
+date = "2021-03-25T21:19:51-05:00"
+author = "bbaovanc"
+cover = "/blog/media/checkra1n-gui-on-arch-linux.png"
+tags = ["linux", "archlinux", "jailbreak", "checkra1n"]
+keywords = ["checkra1n", "gui", "linux", "arch linux"]
 
 description = """
 You can run the GUI version of checkra1n on non Debian-based distributions.
 """
 
-tags = [
-  "guide",
-  "linux",
-  "archlinux",
-  "jailbreak",
-  "checkra1n",
-]
+showFullContent = false
+toc = true
 +++
 
-![Checkra1n GUI running on Arch Linux](/media/checkra1n-gui-on-arch-linux.webp)
-
 ## Introduction
 
 The official cross-distribution build of checkra1n only contains a CLI and TUI.

content/posts/edited-in-middle-of-message-discord.md

@@ -1,24 +1,19 @@
 +++
 title = "Put (edited) in the middle of a message in Discord"
-date = "2021-03-25"
-aliases = [
-  "posts/edited-in-middle-of-message-discord/",
-]
+date = "2021-03-25T18:48:34-05:00"
+author = "bbaovanc"
+cover = "media/discord-tricks/edited-in-middle-of-message.png"
+tags = ["discord", "discord-tricks"]
+keywords = ["discord", "edited"]
 
 description = """
 With a bit of trickery using the RLE character (U+202B), you can get the
 (edited) text on a message to be somewhere other than at the end of the message.
 """
 
-tags = [
-  "tutorial",
-  "discord",
-  "discord-tricks",
-]
+showFullContent = false
 +++
 
-![Example image](/media/discord-tricks/edited-in-middle-of-message.webp)
-
 ## Tutorial
 
 1. Copy the "right-to-left embedding" character (U+202A) to your clipboard.

content/posts/sed-text-substitution-in-discord.md

@@ -1,22 +1,18 @@
 +++
 title = "Text Substitution in Discord using `sed`"
-date = "2021-03-25"
-aliases = [
-  "posts/text-substitution-in-discord-using-sed/",
-]
+date = "2021-03-25T18:48:15-05:00"
+author = "bbaovanc"
+tags = ["discord", "discord-tricks"]
+keywords = ["discord", "sed", "text", "replacement"]
 
 description = """
 Discord has (very primitive) support for text replacement using `sed` syntax.
 """
 
-tags = [
-  "tutorial",
-  "discord",
-  "discord-tricks",
-]
+showFullContent = false
 +++
 
-## Tutorial
+## How-to
 
 [Example Video](/blog/media/discord-tricks/sed-text-replacement.mov)
 

content/referral-codes.md

@@ -1,15 +0,0 @@
-+++
-title = "Referral Codes"
-menu = "main"
-aliases = [
-  "/referrals/",
-]
-
-description = """
-Referral codes for various services that I use/have used
-"""
-+++
-
-- [Vultr](https://www.vultr.com/?ref=8643438-6G)
-  - You get $100 to try out the service for a month
-  - I get $25 if you stay.

layouts/_default/baseof.sql.sql

@@ -0,0 +1,17 @@
+    DROP TABLE IF EXISTS db.blog;
+    
+    CREATE TABLE db.blog (
+        id INT NOT NULL AUTO_INCREMENT,
+        published DATE NOT NULL,
+        title TEXT NOT NULL,
+        body TEXT NOT NULL,
+        url varchar(2048) NOT NULL,
+        CONSTRAINT id_PK PRIMARY KEY (id)
+    )
+    ENGINE=InnoDB
+    DEFAULT CHARSET=utf8mb4
+    COLLATE=utf8mb4_general_ci;
+    CREATE FULLTEXT INDEX blog_body_IDX ON db.blog (body);
+    
+    {{ block "main" .}}
+    {{ end }}

layouts/_default/home.sql.sql

@@ -0,0 +1,13 @@
+{{ define "main" }}
+{{ range (where .Pages "Section" "ne" "gist") }}
+        {{ range .Pages }}
+        INSERT INTO db.blog (published, title, body, url)
+        VALUES(
+            '{{ .Date.Format "2006-01-02" }}',
+            '{{ plainify .Title }}',
+            '{{ (plainify .Content) }}',
+            '{{ .Permalink }}'
+        );
+        {{ end }}
+    {{ end }}
+{{ end }}

layouts/_default/single.html

@@ -1,20 +0,0 @@
-{{ define "main" }}
-<h1>{{ .Title }}</h1>
-{{ if eq .Type "blog" }}{{ if not .Params.menu }}
-<p>
-  <i>
-    <time datetime='{{ .Date.Format "2006-01-02" }}' pubdate>
-      {{ .Date.Format (default "02 Jan, 2006" .Site.Params.dateFormat) }}
-    </time>
-  </i>
-</p>
-{{ end }}{{ end }}
-<content>
-  {{ .Content }}
-</content>
-<p>
-  {{ range (.GetTerms "tags") }}
-  <a href="{{ .Permalink }}">#{{ .LinkTitle }}</a>
-  {{ end }}
-</p>
-{{ end }}