Web

This is a short post on how to host multiple Gitlab project pages using a single Gitlab account. This task is actually very simple, but I could not find any documentation on it when I tried a couple weeks ago. I ended up resorting to creating a second Gitlab account. Turns out you do not need to use this hack, and this post will explain how to legitimately host multiple gitlab pages with just one account.

[Read More]

This is a short post on how to host multiple Gitlab project pages using a single Gitlab account. This task is actually very simple, but I could not find any documentation on it when I tried a couple weeks ago. I ended up resorting to creating a second Gitlab account. Turns out you do not need to use this hack, and this post will explain how to legitimately host multiple gitlab pages with just one account.

[Read More]

As I mentioned in the previous post’s footnote, I actually decided to host this site on GitLab primarily because GitLab is awesome (requires no maintenance on my part, has free private repositories, and natively supports Hugo). There is also good documentation on how to use Hugo with Gitlab from both Hugo and GitLab; however, I ran into a couple small issues I felt were worth addressing. Path, not project name, determines your site URL. [Read More]

As I mentioned in the previous post’s footnote, I actually decided to host this site on GitLab primarily because GitLab is awesome (requires no maintenance on my part, has free private repositories, and natively supports Hugo). There is also good documentation on how to use Hugo with Gitlab from both Hugo and GitLab; however, I ran into a couple small issues I felt were worth addressing. Path, not project name, determines your site URL. [Read More]

Why I decided to blog I’ve had a website for almost two years, but I always envisioned this site being more than simply a persistent resume. I dabbled in this more twice before, but I allowed myself to get in my own way. I convinced myself that my website design was not polished enough, my framework was not secure enough, my writing was not professional enough, and, most paralyzingly, my contributions were not big enough to be released in a public platform. [Read More]

Why I decided to blog I’ve had a website for almost two years, but I always envisioned this site being more than simply a persistent resume. I dabbled in this more twice before, but I allowed myself to get in my own way. I convinced myself that my website design was not polished enough, my framework was not secure enough, my writing was not professional enough, and, most paralyzingly, my contributions were not big enough to be released in a public platform. [Read More]

I’ve had a website for a little over a year now, but I recently had several technical experiences that I really want to share with the world. As such, I decided it was time to create a blog. Three weeks and several frameworks later, I decided upon using Hugo. I still think I will ultimately end up switching to Django due to some of the more advanced goals I eventually have for my own cite (namely, hosting my own web CTF), but I felt I was delaying doing what I really wanted to do (writing the posts) while I spent time learning how to leverage all the CMS and blog template features of Django. [Read More]

I’ve had a website for a little over a year now, but I recently had several technical experiences that I really want to share with the world. As such, I decided it was time to create a blog. Three weeks and several frameworks later, I decided upon using Hugo. I still think I will ultimately end up switching to Django due to some of the more advanced goals I eventually have for my own cite (namely, hosting my own web CTF), but I felt I was delaying doing what I really wanted to do (writing the posts) while I spent time learning how to leverage all the CMS and blog template features of Django. [Read More]