Typing keyboard

New projects and ideas besides this blog

I am using static site generator (Pelican) for this blog. Now, I have new projects and ideas. I would be adding GitHub repo(s) for cloud-native and DevSecOps stuff. It could be confusing because a MarkDown file could be presented in different use cases. So, I would like to explain the Pros and Cons of each tool and what materials should be placed in them.

Details of my blog, GitHub repo and Wiki.js
Tool name Pros Cons Serving what materials
This blog
  • Static pages
  • Don't need a server for hosting
  • Days or months of customization and development time if you don't use an existing theme
  • Stuff about me
  • Stuff suitable for presenting in a blog style
GitHub repos
  • Presented or listing in directories and files
  • Versioning
  • The layout of MarkDown files is boring
  • Templates, scripts, configuration files
  • Page history, versioning and comparison
  • Supports multiple authors for collaboration
  • Media and assets management
  • Import articles from another Wiki or Markup formats
  • Currently, it won't automatically display files like YAML files, scripts, Jinja2 templates and etc.
  • Need a server (and database) for hosting, minimum RAM should be 2GB
  • Limited customization for layout of articles
  • Documentation
  • Articles, detail instructions
  • Stuff where versioning matters

This blog

I had made lots of customization in this blog. Having a left sidebar for the table of content. A right sidebar is used for icons and links. The layout is similar to AWS documentation. The blog is using Meilisearch for searching. For tables in the articles, it is sortable and have sticky table headers. The blog supports Webmentions. Web analytics is integrated with Goat Counter. Finally, the blog is using PWA (Progressive Web Application) and supports offline browsing.

GitHub repos

The GitHub repos(s) is mainly to be used for storing templates, scripts, configuration files. I would use directories for categorization. Simple to use and store stuff. Here's is the GitHub repo created.

New Wiki using Wiki.js

Wiki.js includes a NodeJS application, an optional PostgreSQL database (Wiki.js 2.x only, future major releases require a PostgreSQL database) and quite a number of integrations like third party identity management (Okta, OpenID and etc.). I am having fun setting it up and run it on AWS with k3s. Besides that, I could test and learn other features like AWS S3 storage and Okta integration during the setup.

The main use case of Wiki.js is for writing long, detail instructions and documentation. One main disadvantage is the cost. I tried to run it with an EC2 instance, RDS and an Elastic IP, without load balancer. The cost is about 0.8 to 0.9 USD per day (about 25USD per month). I got some promotional credits in AWS, which would expire at the end of the year, so it is not a problem for a few months.

Edit: After trying out hosting WikiJS in AWS. I found it is more expensive than I thought.

After this small writeup, it is more clear to me about the distribution of the contents and files. Stay safe and till next time.

Share this post on: TwitterRedditEmailHackerNewsLinkedInFacebookIndienewsFor fed.brid.gy

This website supports Webmention

Webmentions are included inside the static pages.

It needs to regenerate the web pages for the latest Webmentions.

There are no Webmentions for this post.

What if I don't have Webmention in my web site?

You could use Comment Parade to send message. Enter https://commentpara.de as the URL when asked to sign in.